Agent identity: what happens when trust is not available?

TL;DR: C1.ai argues that AI agents break the security model because they are non-deterministic yet not trustable, so controls built for humans or software no longer fit. The answer is runtime authorization against scoped mission intent, not background trust in the actor.

Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “An AI Agent Isn't an Employee and It Isn't Software. That's the Whole Problem.”.

Key questions

Q: What breaks when AI agents are not governed at runtime?

A: Without runtime governance, an agent can shift behaviour after provisioning and still execute actions that were never reviewed in context.

Q: Why do AI agents need separate runtime authentication and authorisation controls?

A: Because agent governance answers who approved the agent and what it should do, while runtime controls decide whether the agent can actually act in a specific system.

Q: How can organisations decide whether an AI agent is over-scoped?

A: Compare the agent’s actual connection paths, data reach, and observed tool sequence with its stated purpose.

Practitioner guidance

• Define mission-scoped agent authorisation Document the allowed goals, tools, and action boundaries for each agent before it enters production, and make those boundaries machine-readable for enforcement.
• Enforce per-action runtime checks Require every agent action to pass through policy evaluation at execution time instead of relying on broad pre-approved access.
• Issue credentials only at the moment of use Replace standing secrets with task-scoped access that is minted for the specific action and revoked immediately after the action completes.

Bottom line: AI agents expose a governance gap because they are goal-driven actors whose behaviour cannot be safely assumed to match human or software control models.

What's in the full article

C1.ai's full post covers the operational detail this post intentionally leaves for the source:

• The podcast context and the exact questions posed to Alex Bovee about trust, reputation, and agent behaviour
• How C1.ai describes agent SSO, MCP Gateway authorisation, and Vault-based secret handling in the product context
• The full runtime control pattern behind the so-called digital background check, including attribution and scope enforcement
• The specific examples discussed, including goal-maxing behaviour and production use without security guardrails

👉 Read C1.ai's analysis of why AI agents need runtime authorisation →

Explore further

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