crowdsec_delete_decision
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.
This record as markdown: /tools/kh0pper-crow/crowdsec-delete-decision.md
What crowdsec_delete_decision does on Crow
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.
Why crowdsec_delete_decision is rated Critical
This tool irreversibly deletes or modifies security policy state (removing bans/blocks). Once a ban decision is lifted, the previous blocking state is unrecoverable without re-applying the ban manually. The blast radius is high because unintended ban removal could expose systems to malicious traffic or compromise security posture.
From the tool's definition Tool description explicitly states 'Lift a specific ban' and 'Destructive — the target IP/range will no longer be blocked'. The operation irreversibly removes a security decision that cannot be automatically restored without manual intervention.
Attacks that exploit this kind of access
The rule that runs crowdsec_delete_decision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crowdsec_delete_decision, this is the rule to start with:
crowdsec_delete_decision is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crowdsec_delete_decision call is checked against it from then on.
Questions about crowdsec_delete_decision
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.
More on Crow, and thousands of servers like it.
Across the catalogue