MCP security vs API security
MCP security differs from API security because a model decides which tool to call and with what arguments, every connected server's tool descriptions share one context, and local servers run code on the machine. Authentication, TLS, rate limits, input validation and logging carry over. Sources were read on 16 Nov 2026.
Facts read on .
How is MCP security different from API security?
MCP security differs because the caller is a model choosing actions at run time. OWASP's cheat sheet puts it directly: in traditional APIs developers control every call, while MCP lets language models decide which tools to invoke, when and with which parameters.
Two consequences follow. Arguments are untrusted even from your own client, since they come from model output shaped by whatever the model has read. And the model sees the tool descriptions of all connected servers at once, which is what makes cross-server attacks possible.
Sources: OWASP MCP Security Cheat Sheet.
Which API controls carry over?
Most of the transport and identity controls carry over unchanged. Require authentication on remote endpoints, validate tokens for the right audience, use TLS for remote connections, apply rate limits, quotas and timeouts per session or tenant, and validate every input.
The MCP authorization specification builds on OAuth 2.1 with resource indicators and protected resource metadata, so existing identity providers do most of the work. Platform tools carry over as well: Azure API Management documents key-based and Microsoft Entra token authentication for MCP servers it manages.
Limits need a different shape for a model that can loop. Count calls per session and per tool rather than per address, and for paid integrations OWASP asks for a cap on total spending per period across all servers, with authorized but unsettled payments counted at their maximum.
Sources: OWASP MCP Security Cheat Sheet; MCP specification: Authorization (2025-11-25); Microsoft Learn: Secure access to MCP servers in Azure API Management.
Which risks are new in MCP?
Tool poisoning, rug pulls, tool shadowing and local server code execution have no direct counterpart in a conventional API. OWASP defines tool poisoning as malicious instructions hidden in tool descriptions, schemas or return values, a rug pull as a server changing its definitions after approval, and shadowing as one server's description manipulating the agent's use of another's tools.
Local servers add a risk of their own. The specification lists a malicious startup command in a client configuration and warns that servers run with the same privileges as the client.
Shared context makes these risks compound. One poisoned server can influence calls to a trusted one, which is why OWASP says to treat each server as a separate security domain and to monitor cross-server data flows, such as credentials from one server appearing in calls to another.
Sources: OWASP MCP Security Cheat Sheet; MCP specification: Security Best Practices (2025-11-25).
What changes for authorization and consent?
Authorization has to cover the person approving the action, not only the token. The specification states that hosts must obtain explicit user consent before invoking a tool, and that there should always be a human in the loop who can deny invocations.
Token handling is stricter than many APIs apply: the server must not accept a token that was not issued for it, and token passthrough to a downstream API is forbidden. OWASP also advises treating tool annotations as hints rather than enforcement.
Sources: MCP specification: Tools (2025-11-25); MCP specification: Authorization (2025-11-25); MCP specification: Security Best Practices (2025-11-25); OWASP MCP Security Cheat Sheet.
What changes for logging and monitoring?
Log the model-driven call, not only the HTTP request. OWASP asks for every tool invocation to be logged with full parameters, user context and timestamps, plus alerts on new tools being called, admin-level queries and unusual call frequency.
Gateways that sit in front of servers form a separate category that this site does not cover.
Include the hash of the tool description in the record, so a later investigation can tell which version of the tool the model saw.
Sources: OWASP MCP Security Cheat Sheet.
Sources
- OWASP MCP Security Cheat Sheet (cheatsheetseries.owasp.org), read
- MCP specification: Authorization (2025-11-25) (modelcontextprotocol.io), read
- MCP specification: Security Best Practices (2025-11-25) (modelcontextprotocol.io), read
- MCP specification: Tools (2025-11-25) (modelcontextprotocol.io), read
- Microsoft Learn: Secure access to MCP servers in Azure API Management (learn.microsoft.com), read