Lift a specific ban by its decision ID. Destructive — the target IP/range will no longer be blocked by any bouncer. Use this to undo a false-positive ban.
AI agents call crowdsec_delete_decision to permanently remove resources in Crow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a security decision (ban). While the stated purpose is to correct false positives, the action itself permanently deletes the ban decision. This is a destructive operation because: (1) it cannot be undone without manual re-creation, (2) it modifies the security posture of the system, and (3) an AI agent with malicious intent could abuse it to lift bans on malicious IPs.
From the tool's definition 'Lift a specific ban by its decision ID. Destructive — the target IP/range will no longer be blocked by any bouncer. Use this to undo a false-positive ban.' The tool explicitly deletes/removes a ban decision, which is irreversible.
Documented attack patterns abuse exactly the kind of access crowdsec_delete_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crowdsec_delete_decision:
{
"version": "1",
"default": "deny",
"hide": [
"crowdsec_delete_decision"
]
}crowdsec_delete_decision disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Lift a specific ban by its decision ID. Destructive — the target IP/range will no longer be blocked by any bouncer. Use this to undo a false-positive ban. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crowdsec_delete_decision: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crow. Nothing to install.
crowdsec_delete_decision is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the crowdsec_delete_decision rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for crowdsec_delete_decision. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
crowdsec_delete_decision is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.