Check whether your MCP tools still need authorization

The prompt

For every MCP-exposed tool in this project, confirm there's an authorization check downstream of it — not just a standardized interface. Where does authentication happen, and where does contextual authorization happen?

Why it's built that way

MCP standardizes tool interaction but does not remove the need for authorization. A Gateway can centralize discovery and invocation, Identity handles authentication, and Policy applies contextual authorization to data-plane actions — three distinct jobs, easy to assume one covers the others.

What to do with the answer

If any tool has standardized interaction but no policy check behind it, that tool is the priority fix.