token passthrough
An anti-pattern in which a server accepts a client's token and forwards it to another service instead of getting its own.
A forwarded token lets one compromised server act with the user's access on every service that accepts it.
In more detail
The MCP specification forbids it: it skips the downstream service's checks, breaks audit trails and lets a stolen token reach further. A server needing upstream access should get its own token, for example through token exchange.
Related terms
- MCP authorisation — The part of the MCP specification that protects remote servers with OAuth: the server acts as a resource server and accepts only bearer tokens issued for it.
- token exchange — Trading one proof of identity, such as a platform-issued workload token, for another token that a target service accepts.
Taught in
- Remote Servers And Trust — AI Engineering: LLM Apps, RAG & Agents
References
- MCP: Security best practices (token passthrough, local server compromise, scope minimization)
- IETF RFC 8693: OAuth 2.0 Token Exchange (delegation)