Topic starter
02/08/2026 9:44 am
TL;DR: Model Context Protocol gives AI agents a standard way to reach enterprise tools and data, but it also creates new exposure across identity, authorization, prompt integrity, and shadow infrastructure, according to Salt. The governance gap is now the lack of visibility and control around agent-to-tool connectivity, not the protocol itself.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Understanding the Importance of MCP Security”.
Key questions
Q: What breaks when MCP server discovery is missing from security controls?
A: Without MCP discovery, security teams cannot see which tools an agent can reach or what those tools are allowed to do.
Q: Why do MCP servers increase risk when tool permissions are too broad?
A: MCP servers can expand risk because they sit between an AI client and sensitive backends, often with enough reach to query data, trigger workflows, or modify records.
Q: What are the signs that MCP governance is failing?
A: Common signs include agents reaching systems outside their intended workflow, incomplete audit trails for tool use, and data retrieval that cannot be tied back to a clear business purpose.
Practitioner guidance
- Establish continuous MCP server discovery Inventory servers across endpoints, workstations, containers, CI/CD systems, and cloud instances, then classify each by owner, exposed tools, authentication status, and sanctioning status.
- Enforce authentication and scoped authorization Require explicit identity checks for every MCP interaction and deny unauthenticated access to sensitive tools, data sources, or workflows.
- Sanitize tool output and JSON-RPC payloads Validate schemas before execution, treat server-supplied context as untrusted, and isolate deserialization or command paths that could reach privileged systems.
Bottom line: MCP introduces a new governance layer for AI agents because it standardizes access to tools, data, and workflows across the enterprise.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:37 pm
MCP is not just another integration pattern, it is a governance layer for agentic access. Once an AI system can discover tools and execute actions through a shared protocol, the question changes from connectivity to authority. The relevant control plane is no longer only API security or IAM in isolation. It is the combined governance of agent, client, server, and downstream resource, which means identity teams must treat MCP as a first-class part of the access model.
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.
- 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 is the difference between API security and MCP security?
A: API security focuses on protecting known endpoints and request boundaries. MCP security must also govern the agent’s state, the context it carries, and the sequence of tool actions it can trigger. In practice, that means moving from endpoint-centric controls to workflow-centric access policy and continuous enforcement.
👉 Read our full editorial: Model Context Protocol security exposes a new governance gap