Block bulk deletes
What it does
Blocks any delete that touches more than 100 records in one action, so a looping agent cannot wipe a table.
Default mode in this template: ENFORCE. The “Use in Vulnify” link preselects monitor mode; you can switch to enforce before applying.
Policy
{
"name": "block-bulk-delete",
"description": "Blocks any delete that touches more than 100 records in one action, so a looping agent cannot wipe a table.",
"enabled": true,
"action": "DELETE",
"condition": {
"minRecords": 101
},
"decision": "BLOCK",
"mode": "ENFORCE"
}apiVersion: vulnify.io/v1
kind: Policy
metadata:
name: block-bulk-delete
spec:
description: "Blocks any delete that touches more than 100 records in one action, so a looping agent cannot wipe a table."
enabled: true
action: DELETE
condition:
minRecords: 101
decision: BLOCK
mode: ENFORCEExample test cases
| Case | Input | Expected decision |
|---|---|---|
| agent deletes 10,000 rows | {"agent":"example-agent","action":"DELETE_DATA","resource":"orders-db","recordsAffected":10000} | BLOCK |
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.