Agents

An agent is a first‑class, governed identity — not an anonymous client. Registering an agent is what lets policy reason about “this agent, acting for this user, on this surface” instead of just “some caller.”

What an agent carries

• Owner — the team or person accountable for it.
• Scope — the environments and client surfaces it may operate in.
• Delegated context — the user identity it acts on behalf of at runtime.
• Lifecycle — submission, approval, and revocation, like other governed objects.

Discover vs. call

Policy distinguishes two actions. An agent’s catalog is filtered to what it may discover, and each call is independently authorized. An agent can be allowed to see a tool but denied a particular invocation based on context (surface, environment, credential mode). Tools it can’t discover are simply absent — see Authorization & policy.

Revocation

Revoking an agent (or a break‑glass emergency disable) propagates through the projection and takes effect on the next request, tearing down active sessions. See Emergency-disable a resource.

Note

Register and govern agents the same three ways as everything else — see Register an agent for the UI, API, and CLI.