Topic starter
20/08/2026 5:50 pm
TL;DR: Model Context Protocol traffic bypasses legacy DLP, IAM, and SIEM because it looks like legitimate API activity, transforms sensitive data semantically, and moves exfiltration into tool calls, according to Nightfall. The control gap is not visibility at the perimeter but protocol-aware governance that preserves identity, context, and policy at the agent boundary.
Editorial analysis by NHI Mgmt Group, based on content published by Nightfall: “How does MCP bypass traditional security tools?”.
Key questions
Q: What breaks when MCP servers are connected without a trusted control plane?
A: Discovery and execution become the same decision, which removes the ability to review who published a tool, who can call it, and what trail exists after use.
Q: Why do MCP-connected agents increase risk even when traffic looks legitimate?
A: Because legitimacy at the transport layer does not mean legitimacy at the policy layer.
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
- Inventory every MCP connection Continuously discover MCP servers across desktop assistants, IDE plugins, and custom agent platforms, then remove any unapproved endpoint from the approved registry.
- Bind human identity to every tool call Log the human initiator, the non-human identity used by the agent, the tool invoked, and the returned data classification in one auditable record.
- Shift detection from patterns to meaning Inspect prompts, tool outputs, and responses for semantic leakage of sensitive data such as roadmaps, financials, customer records, and proprietary code.
Bottom line: MCP creates a governance gap because legacy DLP, IAM, and SIEM were built for stable user identities and predictable file movement, not agent-mediated tool calls.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
20/08/2026 6:29 pm
MCP creates a protocol-level governance gap, not just a new data-loss channel. The article shows that traditional controls fail because they inspect the wrong abstraction layer. DLP looks for known content, IAM assumes stable human attribution, and SIEM expects logs at application boundaries. MCP shifts all three assumptions into the agent layer, so the meaningful control point becomes the protocol itself. Practitioners should treat MCP as a new governance surface with its own discovery, inspection, and policy 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.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: How should teams govern MCP when it starts carrying long-running agent work?
A: Treat long-running MCP work as a governed execution state, not a simple API call. Security teams should define ownership, expiry, cancellation authority, and logging for each task so work cannot continue outside the intended policy boundary. That approach matters because the protocol is shifting from transient tool use toward durable agent operations.
👉 Read our full editorial: MCP bypasses legacy DLP and IAM because identity breaks