Agentic AI protocols: what they mean for IAM and security teams

TL;DR: Agentic AI systems do more than answer prompts, because they plan, decide, and act through protocols such as MCP and A2A, according to Black Kite research. That shifts governance from prompt review to identity, delegation, and tool access control, where standing credentials and weak authorisation become the real risk boundary.

Editorial analysis by NHI Mgmt Group, based on content published by Black Kite: “Understanding Agentic AI & Protocols:”.

Key questions

Q: How should security teams govern AI agents that can access enterprise systems?

A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.

Q: Why do agentic AI workflows create new IAM risk compared with traditional automation?

A: Traditional automation usually follows fixed rules and predictable paths, so its access model is easier to review.

Q: What breaks when organisations treat agent identities like service accounts?

A: What breaks is accountability.

Practitioner guidance

• Map every agent authority path Document which tools, datasets, and external actions each agent can reach, then identify where authority is delegated, inherited, or reissued.
• Separate protocol access from model access Treat MCP or A2A connectivity as a control boundary and require explicit approval for each tool or peer connection the agent can invoke.
• Inventory agent credentials as NHIs Track tokens, API keys, and service credentials used by agent workflows with the same lifecycle controls you apply to workload identities.

Bottom line: Agentic AI changes the security problem from prompt control to authority control, because the system can take actions rather than only generate text.

Explore further

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