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

MCP security best practices

The MCP project's security guidance covers confused deputy proxies, token passthrough, SSRF during OAuth discovery, state handle hijacking, local server compromise, malicious authorization URLs, and scope minimization. Independent research adds tool poisoning, where instructions hide in tool descriptions, and cross-server attacks. You can use both to review any server before approval.

Read in this order

  1. OfficialSecurity Best Practices (Model Context Protocol)Start here: the official attack list with a mitigation for each.
  2. ArticleMCP Security Notification: Tool Poisoning Attacks (Invariant Labs)The original tool poisoning demonstration, with concrete malicious descriptions.
  3. OfficialA Practical Guide for Securely Using Third-Party MCP Servers 1.0 (OWASP GenAI Security Project)A checklist for vetting and running third-party MCP servers.

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.