Mandates
Set the rules for actions routed through Oxagen. Each agent works under its own identity, permissions, toolbelt, steering, and budget, and together those terms make up its mandate.
The Mandates tab of the Guardrails page, with illustrative data. Each row is one grant to one agent, such as invoice-bot's mandate for monthly infrastructure invoices under PO-4471, active until Dec 31, 2026, beside a revoked mandate for vendor payouts.
Controls on routed calls
An agent with a standing token can merge to main at 3 a.m., and the team finds out when the deploy breaks. When a call is routed through Oxagen, a rule your team wrote answers it first. The rule allows the call, denies it, or routes it to a named person, and a denied call does not reach the tool.
Oxagen checks those terms on calls routed through it and records each decision, so the people who set the limits can see how they applied.
The rules table on the Guardrails page, with illustrative data. Small refunds to known customers approves Stripe refunds of $500.00 or less and has approved 212 calls and held 9. Weekday dependency bumps has approved 64 and held 2, and Repeat deploys to staging is off.
Parts of a mandate
| Part | What it sets | How it changes |
|---|---|---|
| Access | The consequences the agent may act on, with an expiry | A grant by a person who holds the organization role the workspace names for each consequence |
| Budget | Limits on what the agent may spend and how many calls it may make | An update to the mandate's limits |
| Rules | Whether a routed call is allowed, denied, or sent to a person | The workspace's decision rules |
| Tools | The tool patterns the agent may call | A grant names patterns that must match a declared tool |
| Steering | The instructions a run reads when it starts | A reviewed steering pull request |
Where controls apply
In scope
- Tool calls and model calls that pass through Oxagen's hooks or its local gateway.
- Agent requests checked against the agent's own role and its delegation ceiling, on every plan.
- Observe mode, where Oxagen records what the policy would decide and lets the call go ahead. Budget and model limits still apply to model calls routed through Oxagen.
Out of scope
- Actions the agent's computer never reports to Oxagen.
- Cursor's model calls, which go to Cursor's own servers, so budget limits on model calls do not reach them.
- Asking a person on harnesses that cannot hold a call. Codex and Cursor get a denial with the reason instead.
Product walkthrough
Review the authority, tools, and budget for one supported agent.