Define per-transaction limits, daily caps, counterparty restrictions, and human escalation triggers. The engine evaluates every payment against all active policies in under 10ms.
Per-transaction, daily, weekly, and monthly spending caps. The engine tracks counters atomically in Redis with TTL-based expiration.
Maximum transactions per hour and unique counterparties per day. Prevents rapid-fire spending and counterparty diversification attacks.
Whitelist and blacklist addresses. Agents can only send to approved counterparties. Unknown addresses trigger policy violation.
Operating hours and blocked days. Restrict agent spending to business hours in a specific timezone. Block weekends or holidays.
Allowed and blocked spending categories. Permit compute purchases but block gambling. Categories are defined per transaction.
Limit agents to specific blockchains. A Base-only agent cannot spend on Ethereum. The engine rejects cross-chain attempts.
Transactions above a threshold require human approval. Define the amount, set an approval timeout, and choose the auto-action (reject or allow) when the timeout expires.
Each policy runs in one of three enforcement modes. Start with audit_only to observe agent behavior, move to warn for visibility, then switch to enforce when the rules are calibrated.
Violations logged. Transactions proceed. Use this to understand spending patterns before setting limits.
Violations logged and flagged. Transactions proceed with a warning attached. Dashboard highlights the issue.
Violations reject the transaction immediately. The agent receives a structured error with the violated rule and action taken.