Govern
Authorize actions, filter content, and set usage limits for governed agent traffic
Govern applies the controls that decide what agents can do, what content may pass, and how much spend is allowed. You authorize with Rules, inspect traffic with Guards, and cap model spend with Quotas.
The three controls
Rules
Make deterministic allow and deny decisions for an agent, action, and resource, reading request arguments and verified end-user claims.
Guards
Inspect request and response content on model and tool connections. Filters are a Guard type.
Quotas
Cap LLM spend over a window for a workspace, agent, Gateway, pool, model, or verified end user.
Rules assistant
Draft Cedar from natural language when you would rather describe the intent than write the policy.
Simulate
Check a change against real requests before it affects production behavior.
At runtime, Dome evaluates applicable Quotas, then Rules, then Guards on the content path. Each control fails closed: exhausted limits, unavailable authorization, and blocking Guards stop the request or response. Exhausted total caps reject the call, while exhausted model budgets can spill to another pool member.
See Architecture for where these controls sit in the request path.
Typical workflow
- Authorize access by writing, validating, simulating, and applying Cedar Rules.
- Create Guards and assign Filters to the connections that need inspection.
- Set usage limits at the scopes that own the budget.
Afterward you can revise Rules, roll Filters forward or back, and adjust Quotas without rewiring Connect entities.
Next steps
Connect
Register agents and delegated agents, attach resources, and expose Gateways.
Operate
Investigate audit events, stream live activity, and subscribe external systems.
Manage
Administer access, environments, integrations, and exports.
Develop
Send credentials, Gateway endpoints, and Act-As envelopes from your application.