Agent Allowances
An AI agent's spend per transaction: within its allowance it proceeds, above it a person approves; unidentified agents always go to a person.
- Key
- agent_allowance
- Version
- agent_allowance-v1
- Rules
- 5
- Domain
- AGENT_SPEND
Rules, in the order the evaluator tries them
Highest priority first. The first rule whose conditions all hold decides; with none, the decision is a REVIEW.
Escalate an amount in a currency the template does not list
priority 1000agent-currency-unlisted · AGENT_SPEND
When- context.currency not in ["USD"]
ThenESCALATE → ESCALATE · elevated · SLA 60 min
An amount with no currency, or in a currency without limits, cannot be compared with a limit, so a person decides it.
Escalate spend by an agent that is not identified
priority 500agent-unidentified · AGENT_SPEND
When- agent_safe.actor.id is absent
ThenESCALATE → ESCALATE · elevated · SLA 60 min
An allowance belongs to a named agent; spend nobody can attribute is decided by a person.
Escalate a spend above the agent's allowance
priority 200agent-above-allowance · AGENT_SPEND
When- amount > 100
ThenESCALATE → ESCALATE · elevated · SLA 60 min
A spend above the starter allowance of 100 per transaction needs a person. Replace the allowance with your own; totals over time are the exposure ledger's cumulative limits.
A listed spend within the agent's allowance
priority 100agent-within-allowance · AGENT_SPEND
When- transaction_type in ["purchase", "subscription", "payment_release"]
- agent_safe.actor.id exists
- amount > 0
- amount ≤ 100
ThenAUTO_APPROVE → APPROVE
A listed spend by an identified agent at or under the starter allowance of 100 proceeds.
Escalate every other agent action
priority 0agent-out-of-policy · AGENT_SPEND
WhenThenESCALATE → ESCALATE · elevated · SLA 60 min
An unlisted action, or one with no amount or a non-positive amount, is not within the allowance: a person decides.
Evaluate under it
Locally, with @decionis/mcp: the payload becomes the request's context, and its action the decision type. On the hosted protocol, once the bundle is stored for your organization, name vertical_pack, policy_version and require_exact_policy_version: true. @decionis/mcp 0.4.0 does not carry this pack: the hosted protocol decides a hosted gateway's requests under it.
decionis_evaluate arguments
{ "policy_pack": "agent_allowance", "payload": { "action": "<decision type>" } }In a hosted evaluate-decision request
"vertical_pack": "agent_allowance",
"policy_version": "agent_allowance-v1",
"require_exact_policy_version": trueWorkflow keys that resolve to this pack: agent_allowance.
What its rules read
amount, transaction_type are fields of the request itself, not of its context. A value put only in the context is discarded, and the evaluator holds the decision as an ESCALATE rather than decide without it. @decionis/mcp puts the whole payload in the context, so a payload that carries amount, transaction_type is held.
- agent_safe.actor.id
- amountrequest
- context.currency
- transaction_typerequest
Signals it maps
- auto_clear_ratiofinance_workflow
- escalation_ratiofinance_workflow
- above_allowance_countfinance_workflow
