Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

Best practiceMCP servers and tools

Pin approved MCP servers to their tool list and re-check on every change

OWASP ASI04OWASP ASI02

A server that passed review can change its tools in the next release (a "rug pull") or at runtime. MCPoison showed a config approved once in Cursor stayed trusted after it was swapped for a malicious one.

What to do

  1. Store the approved tools/list result (names, descriptions, schemas) with a hash next to the version.
  2. On every version bump, or on connect, diff the live tool list against the approved one and block on any change until re-reviewed.
  3. Require re-approval when a tool gains write, network, messaging, payment or credential capabilities.

Sources

Check your own AI plan against the practices: Plan check