Topic starter
20/08/2026 5:49 pm
TL;DR: MCP has become a primary integration layer for AI agents while legacy DLP cannot see the protocol, leaving secrets, corporate IP, and overbroad tool use largely ungoverned, according to Nightfall. The core problem is not just visibility but the mismatch between agent-driven tool calls and controls built for files, browsers, and emails.
Editorial analysis by NHI Mgmt Group, based on content published by Nightfall: “MCP Security in 2026: 5 Risks Hiding in Your AI Agent Stack”.
Key questions
Q: What breaks when MCP activity is not visible to security teams?
A: When MCP activity is invisible, traditional DLP and audit controls miss the protocol where AI agents are moving secrets, corporate IP, and privileged actions.
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: 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.
Practitioner guidance
- Deploy protocol-level MCP discovery Continuously inventory MCP servers, tool registrations, and new capabilities so unapproved servers do not remain invisible until after they have connected to internal systems.
- Scope every tool to the minimum verb set Restrict each MCP tool to the smallest action set that supports the use case, and block high-risk actions such as branch creation, message posting, or record deletion unless explicitly approved.
- Inspect sensitive context before it leaves the endpoint Add content inspection for secrets, customer data, and corporate IP at the protocol layer, because MCP payloads are assembled at runtime and will not match traditional DLP signatures.
Bottom line: MCP security exposure is growing because AI agents now move sensitive context through a protocol layer that traditional DLP does not inspect.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
20/08/2026 6:29 pm
MCP security risks are fundamentally a protocol-governance problem, not just a DLP gap. Once AI agents can move sensitive context through tool calls, the inspection model has to shift from file-centric controls to protocol-aware enforcement. The old assumption was that data loss would show up in browsers, email, or cloud sync. That assumption no longer holds, and practitioners need to govern the transport layer where agent activity now lives.
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: Should organisations treat MCP servers like ordinary plugins or like privileged identities?
A: Organisations should treat MCP servers like privileged identities, because they are not passive extensions. They execute inside trusted workflows, make file and API access possible for agents, and can widen the blast radius of a compromise if their permissions are not tightly scoped and continuously revalidated.
👉 Read our full editorial: MCP security risks in 2026 expose a DLP visibility gap