TL;DR: MCP creates a governance problem in AI SOCs because traces, prompts, and tool calls can all carry sensitive evidence, according to Corelight. SOC workflows need stricter handling of telemetry, attribution, and action boundaries as those copies of evidence spread.
Editorial analysis by NHI Mgmt Group, based on content published by Corelight: “What the Black Hat NOC taught me about MCP & agentic SOCs (Chapter 4 of 4)”.
Key questions
Q: Why do traces and prompts need the same controls as security logs?
A: Because traces often contain copies or summaries of the same sensitive data the original logs hold.
Q: What are the signs that an AI agent is overstepping its intended SOC role?
A: Warning signs include agents taking actions outside their assigned workflow, touching tools they do not need, making repeated escalations without clear evidence, or creating case changes that analysts cannot easily explain.
Q: What breaks when an AI SOC uses MCP without a governance harness?
A: Without a governance harness, MCP can blur attribution, expand tool access, and expose sensitive traces to people or processes that were never meant to see them.
Practitioner guidance
- Define read-only versus execution workflows Allow the agent to summarize, pivot, and retrieve first, then gate any action that can change state, touch production data, or modify code.
- Bind every prompt and action to a named human Require an identity layer that makes each analyst prompt, query, and tool invocation attributable, especially in multi-user environments.
- Treat traces like source telemetry Store prompts, outputs, and execution records under the same access controls and retention rules as the logs they were derived from.
Bottom line: MCP in the SOC creates a governance problem as much as a technical one because traces, prompts, and tool calls can all carry sensitive evidence.
Glossary terms: Model Context Protocol, Prompt Injection (Agentic), Trace Retention, Task-Scoped Access
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Harness governance is now the primary control plane for MCP risk. The article makes clear that the protocol is not the hard part; the hard part is the wrapper around it, where attribution, access scope, trace handling, and execution limits are decided. That shifts security ownership away from the model alone and toward the workflow that binds model, logs, and tools together. In practice, teams that treat MCP as a mere integration layer will miss the real attack surface.
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: How should teams separate AI assistance from human accountability in SOC operations?
A: Teams should let AI enrich, correlate, and propose, while humans own escalation, approval, and post-incident review. That separation needs to be written into workflow policy so a tool can never silently convert analyst support into unsupervised response authority.
👉 Read our full editorial: MCP for AI SOCs succeeds only when the harness is governed