TL;DR: MCP, A2A and ACP can move agent tasks, but not delegated authority, approval or revocation, according to Agentic Fabriq. Governance has to be enforced above the wire protocol if policy is meant to survive handoffs and downstream hops.
Editorial analysis by NHI Mgmt Group, based on content published by Agentic Fabriq: “The Agent Protocol Stack in 2026: What MCP, A2A, and ACP Each Solve”.
By the numbers:
- A six-dimension governance taxonomy scores five agent protocols at 2 out of 12 or worse, with voting, dissent preservation and human escalation absent from all five.
Key questions
Q: Why does protocol adoption not prove governance readiness for AI agents?
A: Adoption shows that teams are installing the standards, not that those standards can enforce policy.
Q: Where should approval for agent actions be enforced?
A: Approval should be enforced in the control plane that every hop must pass through, not inside the protocol itself.
Q: What breaks when delegated agent authority is not tied to an authenticated device?
A: The trust chain loses its anchor.
Practitioner guidance
- Define a delegation control plane Centralise who may authorise agent actions, what constraints apply, and when that authority expires, instead of scattering those decisions across protocols and tools.
- Preserve principal correlation across hops Require every agent-to-tool and agent-to-agent transaction to carry a durable link between the human requester and the acting identity, even when the protocol does not standardise it.
- Enforce approval outside the protocol Treat approval as a control-plane state that must be checked before any cross-boundary action executes, because the wire protocol will not do that validation for you.
Bottom line: Agent interoperability is advancing faster than governance semantics, leaving delegated authority and revocation outside the protocol layer.
Glossary terms: Delegated Authority Model, Protocol Governance Semantics, Identity correlation, Control-plane enforcement
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Protocol maturity does not equal governance maturity: The article correctly separates transport standardisation from authority control. That distinction matters because many teams read adoption numbers as if they were evidence of governance readiness, when they are only evidence of deployment. The missing layer is not another protocol feature; it is a governance function that sits above the wire format. Practitioners should stop treating interoperability standards as if they already solve accountability.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between protocol transport and governance semantics?
A: Transport moves messages between systems, while governance semantics define who may act, under what limits, and how that authority is revoked. MCP, A2A and ACP address the first problem well enough for their own layers, but they do not standardise the second. Practitioners need both, and the governance layer must be enforced separately from the wire protocol.
👉 Read our full editorial: Agent protocol stacks still omit delegated authority and revocation