Why MCP Connectors Need a Structured Review Process
Model Context Protocol connectors extend what an AI system can see and do, which means each connector introduces its own authentication model, permission surface, and data flow. Without a consistent review process, these differences get evaluated inconsistently, or not at all, before a connector reaches production.
What MCP Does and Does Not Enforce
MCP's specification defines OAuth 2.1 as the authorization flow for HTTP-based remote servers, but it explicitly leaves local stdio servers outside that requirement. It also does not standardize an audit log format across implementations. Reviewers should treat these as gaps to close with documented compensating controls rather than assumptions to leave unverified.
Transport Type Changes the Risk Profile
A stdio server running locally and a Streamable HTTP server running remotely present different attack surfaces. Confirming the transport type at the start of a review determines which controls are even applicable.
Tool Definitions as an Injection Surface
Tool names, descriptions, and input schemas are passed to the model as context. Because this metadata originates from the server rather than the host application, unvalidated or manipulated tool descriptions can be used to inject instructions, a risk generally referred to as indirect prompt injection. Reviewing tool definitions for scope beyond documented business need is therefore a security control, not a formality.
Governance Practices for Ongoing MCP Trust
A static review at deployment time is necessary but not sufficient. Sustained trust in an MCP connector depends on governance practices applied consistently over time:
- Treat MCP server trust as non-transitive: approving one server's tools does not extend trust to other servers or downstream systems it may call
- Require documented data flow mapping for every server as a condition of approval, not an optional artifact
- Assign clear ownership for periodic reassessment, given that MCP's authorization mechanisms have changed materially within the past year
- Maintain an inventory of consent and approval decisions to support audit and incident response
- Define explicit re-review triggers, including specification upgrades, tool schema changes, and server ownership changes
Where Static Review Ends and Runtime Governance Begins
Static review confirms that a connector should be approved based on its declared authentication model, tool scope, and data flow at a point in time. It cannot detect a tool that begins behaving differently after an update, or a server whose ownership changes silently. That is the boundary where runtime monitoring and policy enforcement take over, providing ongoing verification that a connector continues to operate within its approved scope.