Join our Newsletter — 33% off our NHI Course

Why do MCP and A2A turn AI governance into action control?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: MCP and Agent2Agent shift governance from output quality to authorised action across tools and data sources, according to Collibra. Identity, approvals, and task context now matter as much as model capability when agents can act.

Editorial analysis by NHI Mgmt Group, based on content published by Collibra: “The bookends of AI: Why data and business impact still define success”.

Key questions

Q: Why do A2A workflows increase identity governance risk for AI programmes?

A: A2A increases risk because delegation can move across multiple machine actors before a human sees the result.

Q: How should security teams govern AI agents in shared workspaces?

A: Security teams should treat the workspace audience as part of the authorization decision.

Q: What breaks when AI agents bypass a centralized MCP gateway?

A: When agents bypass a centralized MCP gateway, security controls fragment across notebooks, scripts, and individual servers.

Practitioner guidance

  • Define approved action boundaries for AI agents Document which tool actions, data sources, and workflow steps an AI agent may perform without additional approval.
  • Classify MCP-connected tools as access surfaces Inventory every tool exposed through MCP and assign an owner, purpose, and review cadence.
  • Build delegation controls for A2A workflows Map which agent can hand off work to another agent, what context carries forward, and where the chain must stop for human approval.

Bottom line: MCP and A2A do not just expand AI capability, they change the governance question from output quality to authorised action.

Glossary terms: Model Context Protocol, Agent2Agent Protocol, Action Boundary, Agent Lifecycle Management

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Model Context Protocol creates an authorisation problem, not just an integration problem. Once an AI system can reach tools and data sources through a shared protocol, the governance question shifts to who authorised the action, not whether the model could technically perform it. That means identity controls have to define permissible action space before runtime, because the model is now operating with side effects. Practitioners should stop treating tool connectivity as neutral plumbing and start treating it as a governed access path.

A few things that frame the scale:

  • AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: How do you know when an AI agent has outgrown its current access model?

A: An AI agent has outgrown its access model when it can initiate or complete actions that were never explicitly reviewed as part of the business process. Signs include broad tool reach, unclear handoff points, and approvals that describe intent but not the actual action set.

👉 Read our full editorial: MCP and A2A shift AI governance from output review to action control


This post was modified 7 days ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.