Review changes to financial records
What it does
Any agent write to a financial resource (ledgers, payouts, refunds) waits for an owner or admin to approve. Vulnify does not read amounts, so this covers every write, not a value threshold.
Default mode in this template: ENFORCE. The “Use in Vulnify” link preselects monitor mode; you can switch to enforce before applying.
Policy
{
"name": "fintech-review-financial-writes",
"description": "Any agent write to a financial resource (ledgers, payouts, refunds) waits for an owner or admin to approve. Vulnify does not read amounts, so this covers every write, not a value threshold.",
"enabled": true,
"action": "WRITE",
"resource": "FINANCIAL",
"decision": "REVIEW",
"approverRoles": [
"OWNER",
"ADMIN"
],
"mode": "ENFORCE"
}apiVersion: vulnify.io/v1
kind: Policy
metadata:
name: fintech-review-financial-writes
spec:
description: "Any agent write to a financial resource (ledgers, payouts, refunds) waits for an owner or admin to approve. Vulnify does not read amounts, so this covers every write, not a value threshold."
enabled: true
action: WRITE
resource: FINANCIAL
decision: REVIEW
approverRoles:
- OWNER
- ADMIN
mode: ENFORCEExample test cases
| Case | Input | Expected decision |
|---|---|---|
| agent issues a refund | {"agent":"example-agent","action":"WRITE_DATA","resource":"payments-ledger","recordsAffected":1} | REVIEW |
Try this template on your own agents, in monitor mode first.
Use in VulnifyNot legal advice. These templates are starting points to help you design internal controls for AI agents. They are not legal advice and do not make your organization compliant with LGPD, GDPR, HIPAA or any other law or regulation. Review them with your own legal and compliance team before relying on them. Templates are provided “as is”, without warranty. Whether a rule matches depends on how you classify your resources and on the data your agents send; test in monitor mode before enforcing.
License: the templates are dedicated to the public domain under CC0 1.0. “Vulnify” is a trademark; the CC0 dedication does not cover the Vulnify name or logo.