Practical integration guide · Ravindra Annam

MCP and Tool Authorization Security

Review who can invoke a tool, what that tool may access, and where policy is enforced before an action runs.

By Ravindra AnnamUpdated October 11, 2026All resources →
Secure the service boundary

An authenticated request still needs a limit.

A connection to an MCP server is one boundary in an agent workflow. The downstream application may have a different identity, credential, and permission model. Document both sides before enabling write operations or access to sensitive data.

Separate authentication from permission

The MCP July 28, 2026 authorization guidance uses OAuth-based authorization for HTTP transports; local STDIO deployments have a different credential context. Check the current specification for your transport. Enforce the requested operation and resource in the receiving service.

Validate the intended token audience

MCP security guidance prohibits token passthrough. Validate that the access token was issued for the MCP server, and obtain separately authorized downstream credentials. Test a token intended for another API: the server should reject it.

Treat tool content as untrusted input

Tool descriptions and responses can influence a model's plan. Keep that influence separate from the policy deciding whether a call may run. Start with a narrow set of tools and limit their filesystem, network, and execution access.

Bind application state to the actor

The 2026 protocol is stateless. If an application creates its own workflow handles, bind them to the authenticated principal and enforce access on every use. Do not assume older MCP session mechanisms describe your current implementation.

Constrain outbound connections

Review URL discovery, redirects, and tool fetches for server-side request forgery. Apply destination policy and account for private addresses and DNS changes. Include these checks in integration testing.

A useful acceptance test

Try the same write request with the right actor, the wrong actor, an expired grant, and a changed target. Record which service rejected each forbidden request and whether any downstream action occurred.

Verify the exact protocol version, authorization server behavior, and tool implementation you deploy. Repeat the review when integrations or permissions change.