Topic starter
24/06/2026 7:14 pm
TL;DR: Control plane tools can discover, inventory, and assign ownership to AI agents, but they do not stop an agent from acting three months later when it independently calls tools or provisions infrastructure, according to 1Kosmos. The real governance gap is runtime authorization: existing identity models assume access is stable enough to review, but autonomous agents can create and use privileges inside a single session.
Editorial analysis by NHI Mgmt Group, based on content published by 1Kosmos: “When Control Plane Tools Don't Stop AI Agents from Acting: The Execution Plane Gap”.
Key questions
Q: What breaks when AI governance starts with policy instead of inventory?
A: Policy-first programmes usually stall because teams cannot define scope, boundaries, or ownership with confidence.
Q: Why do autonomous agents need runtime governance instead of simple access controls?
A: Autonomous agents can turn a request into a sequence of actions without a human pausing the workflow for review.
Q: How do security teams know whether an AI agent control stack is actually working?
A: Look for three things: every agent has a traceable identity, permissions are narrow enough to explain in operational terms, and actions can be audited end to end.
Practitioner guidance
- Define the runtime control boundary for agents Map where agent actions become consequential and identify the policy point that must intercept those actions before MCP routes them to tools.
- Separate ownership from authorisation Keep lifecycle ownership records, but require a live authorisation check for each tool call that can change data, infrastructure, or money movement.
- Replace static agent credentials with scoped credentials Use short-lived credentials that bind one agent, one permitted action set, and one validity window instead of reusable API keys.
Bottom line: AI agent governance fails when organisations confuse inventory with runtime control, because ownership records do not stop a live action from executing.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 4:27 am
Inventory without execution control is governance theatre: discovery, ownership, and lifecycle tracking matter, but they do not answer the only question that matters at runtime, which is whether this action should be allowed now. That makes control-plane-only thinking insufficient for autonomous behaviour. Practitioners need to stop treating registration as proof of safety and start treating it as only the first governance layer.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What happens when an agent is allowed to act without a live policy check?
A: The system treats a valid credential as proof enough, even if the requested action is outside the original task or business context. That creates an implicit-trust model where a single agent request can trigger unintended data, infrastructure, or access changes.
👉 Read our full editorial: AI agent governance needs an execution plane, not just inventory