An MCP server can change its tool descriptions after you approve it, which is the rug pull variant of tool poisoning. Pin server versions and lockfiles, hash tool definitions, and rescan when they change. Treat the MCP spec itself as a moving dependency.
Read in this order
- ArticleMCP Security Notification: Tool Poisoning Attacks (Invariant Labs)Start here: the attack that makes pinning necessary.
- Open sourceagent-scan, security scanner for agents, MCP servers, and skills (Snyk, formerly mcp-scan)Scan a server and flag changes to tool descriptions between runs.
- OfficialKey Changes, 2025-11-25 (Model Context Protocol specification)What changed in a spec release, as an example of a moving dependency.