By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

MCP server and tool pinning

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

  1. ArticleMCP Security Notification: Tool Poisoning Attacks (Invariant Labs)Start here: the attack that makes pinning necessary.
  2. 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.
  3. OfficialKey Changes, 2025-11-25 (Model Context Protocol specification)What changed in a spec release, as an example of a moving dependency.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.