TL;DR: The real challenge in a four-week MCP rollout is governing internal API access inside AI sessions, not standing up the protocol itself, according to Archestra. Teams need a clear boundary for authentication, logs, filtering, and credential handling before broader access can scale.
Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “So you're the 'MCP person' at your company now”.
Key questions
Q: Why does MCP gateway governance matter for access control decisions?
A: Because the gateway is where tool invocation is actually approved or denied, and that decision sits closer to runtime action than the original login.
Q: How should teams handle authorisation beneath an MCP layer?
A: They should treat the MCP server as a translation layer, not a trust boundary.
Q: What should security teams govern first in an MCP rollout?
A: Start with API ownership, data sensitivity, and the destructive actions each endpoint can trigger.
Practitioner guidance
- Inventory candidate APIs before building anything List the internal APIs that users want AI to act on, then record the owner, current auth model, destructive endpoints, and business impact of a bad call.
- Place every MCP server behind a gateway Use a single gateway for unified auth, structured audit logs, namespace filtering, credential injection, and version pinning instead of exposing servers directly.
- Delay delegated auth until the base model is stable Get SSO and audit working first, then evaluate on-behalf-of flows and downstream scopes once the organisation has a reliable evidence trail.
Bottom line: MCP rollout should be governed as an access and audit problem, with API ownership and sensitivity defined before any server goes live.
Glossary terms: MCP Gateway, Delegated Authorization, Tool Filtering, Interaction-Level Audit Trail
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP turns API governance into a session-time identity problem. The article is correct to reject the idea that MCP is mainly a protocol rollout. What changes is the context in which APIs are consumed: access now occurs inside an AI session where the client is non-deterministic and the human requester cannot directly inspect every action. That shifts governance from static integration approval to runtime control over scope, evidence, and tool use. Practitioners should treat MCP as a governed access path, not a new class of application.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How do you know an MCP rollout is ready for broader access?
A: Look for boring behaviour in the pilot: tool selection should be predictable, auth failures should be explainable, and logs should show user, tool, arguments, and result consistently. If those signals are not stable in a small internal test, scaling the rollout will only multiply the same governance gaps.
👉 Read our full editorial: MCP rollout is an API governance problem, not a protocol project