The observed tier acts after the fact
For a vendor agent acting inside its own product, the governor reads the audit log, flags an action your rules forbid and can suspend the agent. It cannot stop that single action before it happens.
The Agent Governor is runtime authorization for AI agents: every action is decided by your policy, and you can stop any agent.
Applications
3 cannot sign in
Open issues
4 critical · 7 high
Overdue findings
10 new
AI agents
34 not governed
Agent actions · 24h
52 denied
Waiting on you
Stops in force
1 automatic
Agent coverage
34 discovered agents act with no governor in their pathGovern
Agent actions last 24 hours
2,628 Allowed30 Held52 Denied
Agents you build send their calls through the governor, so it can allow, hold or deny each action before it happens. A vendor agent that lets an admin add external tools can be pointed at the governor and gets the same decision on each action.
For a vendor agent the governor cannot sit in front of, it suspends the agent's identity in Entra, Okta or Salesforce, or reads the platform's audit log, flags actions your rules forbid and can suspend the agent.
Agents you build
The agent's calls go through the governor over MCP or HTTP. The governor allows, holds or denies before the action happens, then mints a short-lived credential scoped to the action and runs it.
Decides: Every action, before it runs
Vendor agents that accept external tools
A vendor agent that lets an admin register external tools or MCP servers is pointed at the governor, which turns its calls into inline traffic.
Decides: Every action, once routed
Vendor agents the governor cannot sit in front of
The governor suspends the agent's identity and revokes its grants.
Decides: The agent's identity
Vendor agents acting inside their own product
The governor reads the platform's audit log every 2, 5, 15 or 60 minutes, flags an action your rules forbid, and can suspend the agent.
Decides: After the fact
Each agent sits in the strongest tier its deployment allows.
| Tier | Fits | Governor decides | Named platforms |
|---|---|---|---|
| Inline | Agents you build | Every action, before it runs | MCP, HTTP |
| Routed | Vendor agents that accept external tools | Every action, once routed | Copilot Studio, Agentforce, Claude |
| Identity bound | Vendor agents the governor cannot sit in front of | The agent's identity | Entra, Okta, Salesforce |
| Observed | Vendor agents acting inside their own product | After the fact | Microsoft Entra, Okta, Salesforce, Microsoft Purview |
a vendor agent that lets an admin register external tools or MCP servers (Copilot Studio, Agentforce, Claude) is pointed at the governor, which turns its calls into inline traffic.
for a vendor agent the governor cannot sit in front of, the governor suspends its identity in Entra, Okta or Salesforce and revokes its grants.
for a vendor agent acting entirely inside its own product, the governor reads the platform's audit log (Microsoft Entra, Okta, Salesforce or Microsoft Purview, every 2, 5, 15 or 60 minutes), flags an action your rules forbid, and can suspend the agent.
Microsoft Entra
Reads the audit log every 2 minutes
Okta
Reads the audit log every 15 minutes
Salesforce
Reads the audit log every 15 minutes
Microsoft Purview
Reads the audit log every 60 minutes
A flagged action names the rule it broke. Suspend the agent from the same row.
Stop one agent, one person's delegations, one target, one vendor or the whole org. Live credentials are revoked. The stop applies at the next decision, and you lift it from the banner when the incident is over.
Automatic stop rules do the same without a person. An agent that racks up denied actions is stopped and its credentials are revoked.
Stop agents
The stop applies at the next decision. Live credentials are revoked.
Guardrails
Stop after denied actions
10
Denials within five minutes that stop the agent and revoke its credentials.
Actions per minute
120
Over the limit, actions are denied until the minute rolls over.
Held actions wait for a person. Two-person approval is available. Your policy sets which actions are held, and the approver decides whether each one runs.
support-copilot · zendesk-apiHoldTwo-person approval
POST /api/v2/tickets/48211/refund
62Held · Hold threshold4m ago
reporting-bot · analytics-dbHold
COPY (SELECT * FROM public.orders) TO STDOUT
60Held · Exports need a person1m ago
J nextK previousA approveD deny
A held action waits in Approvals. The agent gets no credential while it waits.
Approve once runs that exact action. A window covers equal actions until it closes.
A two-person hold shows 1 of 2 until a second, different person approves.
Held actions page the agent's owner and governor admins.
One Inspect overview for applications, findings, AI agents, approvals and stops, with trend lines on every number. Read the band left to right, then work the queue: each row has the button that fixes it.
Inspect pages work on phones, so an approver can decide a held action away from a desk.
2 agent actions are waiting on a person
1 stop is in force
1 automatic
1 governor target has no rules
Every action on it is denied until a rule permits it
3 applications cannot sign in
6 agents can write with no person approving
Found by inspections of your applications
1 application has no way to stop its agents
34 discovered agents are not governed
Discovered agents with no governor in their path
4 overdue findings
2 inspections did not finish
12 applications have never been inspected
support-copilot · zendesk-apiHold
POST /api/v2/tickets/48211/refund
62Held · Hold threshold4m ago
reporting-bot · analytics-dbHold
COPY (SELECT * FROM public.orders) TO STDOUT
60Held · Exports need a person1m ago
J nextK previousA approveD deny
Every decision is logged in a tamper-evident audit log that you can export. When the board or an auditor asks what an agent did, you show the event and prove nobody edited it.
The governor is an identity provider for agents. It issues short-lived signed tokens that name the agent and the person it acts for, verifiable against your org's published keys.
Each hash names the event before it.
Each event carries its own hash and the hash of the event before it, so an edit anywhere breaks every link after it. Illustrative data from a Coverbase demo org.
| Event | Decision | Hash | Previous hash |
|---|---|---|---|
| #4117 | Allow | 9f2c41e7 | 52ab09d3 |
| #4118 | Hold | c07e5a12 | 9f2c41e7 |
| #4119 | Deny | 3b8d6f90 | c07e5a12 |
| #4120 | Allow | e41a7c58 | 3b8d6f90 |
For a vendor agent acting inside its own product, the governor reads the audit log, flags an action your rules forbid and can suspend the agent. It cannot stop that single action before it happens.
When the governor cannot sit in front of a vendor agent, it suspends the agent's identity in Entra, Okta or Salesforce and revokes its grants. It does not decide each action that agent takes.
Each policy set is mapped to requirements in 12 frameworks. Mapping a set to SOC 2 or ISO/IEC 42001 does not make you compliant. Your auditor still assesses your controls.
Bring an agent your team built and one a vendor runs. We put the governor in front of both, stop one, and walk through the trail with you.