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

Confused deputy and token passthrough

An MCP server that forwards a client's token to a downstream API, or uses its own powerful credentials for a user without checks, becomes a confused deputy. MCP security guidance forbids token passthrough and requires per client consent for proxy servers. Audit every server that fronts a third party API for both problems.

Read in this order

  1. OfficialMCP security best practicesStart here: MCP's own rules against token passthrough and unchecked proxying.
  2. Open sourceDamn Vulnerable MCP Server (DVMCP)Hands on: a deliberately vulnerable MCP server to practice tool poisoning and token theft.
  3. OfficialOWASP MCP Top 10Where these flaws sit among the common MCP risks.

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.