Topic starter
11/06/2026 11:01 pm
TL;DR: The new MCP specification adds server identity checks, formal authorization metadata, long-running tasks, HTTP streaming, and registry-based discovery, reflecting a shift from trusted tool access to verifiable agent interactions according to Lakera. That changes the governance problem from simple connectivity to runtime control over what agents can discover, do, and keep doing.
Editorial analysis by NHI Mgmt Group, based on content published by Lakera: “What the New MCP Specification Means to You, and Your Agents”.
Key questions
Q: What breaks when MCP servers are not vetted before use?
A: When MCP servers are not vetted, the enterprise loses control over privileged tool access inside AI workflows.
Q: Why do long-running MCP tasks change the security model?
A: They turn a tool call into durable state.
Q: How do security teams know whether MCP authorization is actually working?
A: Look for evidence that consent is stored per client, tokens are validated at each hop, and invalid audience or redirect values are rejected consistently.
Practitioner guidance
- Verify server identity before tool exposure Require a stable identity record for every MCP server and compare declared capabilities against an approved baseline before any agent is allowed to call tools.
- Formalise authorization metadata for each server Block any MCP integration that does not expose machine-readable permissions, eligible users, and authentication requirements for every tool and resource.
- Track task lifecycle as a security object Monitor task creation, resumption, and completion as separate governance events so long-running agent work cannot disappear between sessions.
Bottom line: MCP is moving agent governance from implicit trust to verifiable control over identity, authorization, and persistence.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 7:29 am
Verifiable discovery is now a governance requirement, not a convenience feature. MCP’s shift toward server identity documents reflects a broader lesson for agentic systems: discovery without verification is just delegated trust. Once agents can pull capabilities from registries or well-known locations, identity becomes part of the policy boundary, not a side detail. Practitioners should read this as a control-plane change, because the thing being governed is no longer just access, but discoverable authority.
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: What is the difference between MCP discovery and MCP provenance controls?
A: Discovery tells an agent what exists, while provenance tells the organisation what is trusted. Discovery is about finding tools and servers; provenance is about proving they are the right ones and that their runtime behaviour matches the approved record.
👉 Read our full editorial: New MCP spec shifts AI agent governance from trust to verification
This post was modified 1 day ago by NHI Mgmt Group