TL;DR: MCP governance must combine curation, admission, runtime enforcement, and audit controls to keep a fast-growing server estate within policy, according to Jozu. Without provenance, scoped access, and tamper-evident records, approved servers can still drift into unsafe runtime behaviour.
Editorial analysis by NHI Mgmt Group, based on content published by Jozu: “What Is MCP Governance? A Framework for Securing MCP Servers at Scale”.
Key questions
Q: Why do MCP servers need both admission controls and runtime enforcement?
A: Admission decides whether a server may load, but runtime enforcement decides what that server can do after it is running.
Q: How do security teams know whether MCP server governance is working?
A: They should be able to answer four questions at any time: what servers exist, which are official, what credentials they can use, and what systems they contact.
Q: What breaks when MCP servers are trusted without registry and admission controls?
A: A trusted MCP server can become a hidden execution path for data theft, unsafe actions or code execution.
Practitioner guidance
- Inventory all MCP server usage Sweep developer desktops, CI/CD pipelines, agent runtimes, and IDE configurations to identify every active MCP server before you define policy.
- Stand up a curated internal registry Mirror approved servers into a signed internal registry with scan results, provenance data, and version pinning so there is one source of truth.
- Separate admission from runtime enforcement Use artifact policy for load-time approval and a distinct runtime policy for tool calls, arguments, approvals, and content boundaries.
Bottom line: MCP governance is about controlling the server estate as a lifecycle problem, not just hardening a protocol endpoint.
Glossary terms: MCP governance, Curated Registry, Runtime Enforcement, Tamper-Evident Audit Trail
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP governance is becoming the practical control plane for model-connected tooling. The article describes a world where servers are no longer isolated integrations but shared execution paths for employees, agents, and assistants. That changes the security problem from endpoint-style hardening to governed access, scoped runtime behaviour, and auditable decisions. Practitioners should treat MCP governance as an identity and control discipline, not a narrow platform feature.
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: Who should own MCP credential governance in an IAM programme?
A: Ownership should sit with the identity or security team that governs other non-human credentials, not with tooling admins alone. These tokens authorize API access and should be treated as part of the organisation’s NHI inventory, scope management, and offboarding process.
👉 Read our full editorial: MCP governance turns server sprawl into auditable control