01
Delegate a narrow action
An agent that can suggest a payment is different from one that can initiate, approve, and settle it. Separate those permissions and begin with the least authority required for the workflow.
02
Make intent verifiable
The system should preserve the triggering request, business purpose, beneficiary, amount, policy evaluation, approvals, tool calls, transaction result, and exceptions in a form that finance and security teams can review.
- Allowlisted counterparties and assets
- Per-transaction and cumulative limits
- Human approval above defined thresholds
- Independent destination verification
- Automatic pause after anomalous or failed behavior
03
Design the revocation path
Teams need an immediate way to revoke credentials, freeze the workflow, rotate keys, and preserve evidence. A capable agent without a clear off switch is not production-ready.