What makes agent governance distinct from general AI governance

General AI governance applies to AI systems that produce outputs: text, predictions, classifications. Agent governance applies to AI systems that take actions — writing to databases, calling external APIs, sending emails, triggering downstream processes. The distinction matters because the risk profile is different: an output that is wrong can be corrected before it causes harm; an action that is wrong may be irreversible. Agent governance must address not just whether the agent produces correct outputs but whether it is authorized to take the actions it takes and whether those actions can be audited and rolled back.

Core controls for agent governance

Identity and authentication: agents should have distinct identities rather than inheriting human user credentials, so their actions can be attributed and scoped. Permission boundaries: agents should operate with least-privilege access — only the tools and data access they need for their defined task. Audit trails: all agent actions should be logged with enough detail to reconstruct what the agent did, why, and what resulted. Operational bounds: hard limits on the number of actions per session, the systems the agent can reach, and the values at stake. Human escalation paths: clear conditions under which the agent stops and defers to a human rather than proceeding autonomously.

The relationship to broader AI governance

Agent governance sits within the broader AI governance structure — it does not replace it. The organization's AI policies define what agents may be used for; agent-specific governance defines how they are operated safely within those bounds. Risk assessments for agent deployments should incorporate the full scope of actions the agent can take, not just the quality of its outputs. Incident response plans need to account for agents taking wrong actions that may require reversal, which is qualitatively different from responding to a model producing a bad output.