TL;DR: Oak warns that MCP server sprawl turns shared, long-lived tokens into unowned machine identities that outlive the work they support, so governance has to track each server's owner, scope, usage and retirement date. Treating servers as identities collapses the gap between access creation and accountability, which is where most exposure accumulates.
Editorial analysis by NHI Mgmt Group, based on content published by Oak: “How to Govern MCP Servers in an Enterprise”.
By the numbers:
- The 2026 Identity Security Landscape found 109 machine identities per human.
- The 2026 Identity Security Landscape found 40% of machine identities have access to organizational data.
Key questions
Q: Why do shared tokens make MCP server access hard to govern?
A: Shared tokens erase attribution because many people and systems use the same credential, so logs show the token rather than the actual actor.
Q: What is the difference between MCP server access and service account sprawl?
A: MCP server access is the permission path an agent or tool uses to call a server, usually through scoped tokens or OAuth grants.
Q: How should teams inventory MCP servers and their credentials?
A: Teams should inventory every MCP server, the downstream systems it reaches and the credentials it uses for each connection.
Practitioner guidance
- Inventory every MCP server and downstream token Record every server, the systems it fronts and the credential used for each downstream connection.
- Assign an accountable owner to each server Name a person or team responsible for each server's credentials, scope and retirement.
- Scope one token per server per system Avoid shared credentials across multiple users or tools.
Bottom line: MCP servers should be treated as machine identities because the tokens they hold determine real downstream access.
Glossary terms: MCP Server, Model Context Protocol, Machine Identity, Credential Sprawl
What's in the full article
Oak's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step governance workflow for registering MCP servers across SaaS, homegrown and shadow environments
- Examples of how to map owners, scopes and end dates to individual server credentials
- A practical control table for distinguishing review, rotation and retirement actions
- The article's own framing for how to present MCP server risk to auditors and board stakeholders
👉 Read Oak's analysis of MCP server credential sprawl and governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shared MCP tokens are really entitlement bundles, not mere setup artefacts. When a server fronts multiple downstream systems, each token becomes a separate access decision that must be owned, scoped and retired. That is why server proliferation creates governance debt even before any attack occurs. Practitioners should treat each token as a distinct entitlement with a lifecycle, not a convenience credential.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should happen to MCP server tokens when a project ends?
A: MCP server tokens should be revoked, rotated and removed from all vaults, configuration stores and environment variables when a project ends. Any standing access tied to the server should be closed so the token cannot keep calling tools or data after the work is over. If the token was shared, every dependent secret should be reissued.
👉 Read our full editorial: MCP server sprawl creates unowned machine identities from shared tokens