TL;DR: Chained AI decisions can spread risk across workflows without a human checkpoint at each step, according to Tumeryk. Inline policy enforcement at prompt and handoff time is the control point that can limit that spread.
Editorial analysis by NHI Mgmt Group, based on content published by Tumeryk: “Agent-to-Agent AI Is Here. Governance Must Catch Up.”.
Key questions
Q: Why do autonomous AI workflows create more security risk than traditional endpoint activity?
A: Autonomous AI workflows create more risk because a command result may no longer map cleanly to a human action.
Q: What are the signs that AI governance is failing in the enterprise?
A: Common warning signs include rapid growth in AI use without matching policy coverage, sensitive files being copied into personal accounts, and a large share of AI apps carrying high or critical risk.
Q: What breaks when AI agents are allowed to contain incidents without governance?
A: The response chain becomes difficult to audit and reverse.
Practitioner guidance
- Define inline approval boundaries for agent actions Require policy evaluation before agents can call tools, hand off tasks or alter shared context.
- Classify each AI agent as a governed identity Assign every agent an owner, scope, lifecycle state and delegation limit so it can be registered, reviewed and retired like any other privileged operational identity.
- Instrument agent interactions for pre-action controls Collect prompts, context changes, tool requests and agent-to-agent handoffs, then enforce rules at execution time rather than relying only on logs and investigations afterward.
Bottom line: Agentic AI creates a governance gap because chained decisions can propagate risk across systems without a human checkpoint at each step.
Glossary terms: Agent-to-agent trust, Inline Governance, Prompt-level trust evaluation, Operational Identity Contact
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agent-to-agent risk is now a governance problem, not a model-quality problem. The article’s central insight is that failures emerge when one agent’s output becomes another agent’s input without policy checks at the point of transfer. That turns orchestration into a security boundary and makes delegation, approval and context handling the real control plane. Practitioners should govern the interaction chain, not just the model response.
A few things that frame the scale:
- 54% of organisations are actively deploying AI agents across workflows, yet only 21% report a mature governance model for agentic AI.
A question worth separating out:
Q: Should organisations treat AI coding agents like privileged software identities?
A: Yes. If an AI agent can install code, access secrets, or modify repositories, it is functionally acting as a privileged non-human identity and should be governed that way. That means task-scoped access, explicit boundaries, and monitoring of its downstream actions, especially when it can touch build and release systems.
👉 Read our full editorial: Agent-to-agent risk exposes the governance gap in autonomous AI