crow_campaign_delete

Delete a campaign and all its posts. Requires confirmation.

SERVERCrow SOURCEkh0pper/crow

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-campaign-delete.md

WHAT IT DOES

What crow_campaign_delete does on Crow

AI agents call crow_campaign_delete 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.

RISK

Why crow_campaign_delete is rated Critical

This tool irreversibly deletes a campaign and all associated posts, which cannot be undone. Even though it requires confirmation, the action itself is destructive in nature, affecting potentially significant amounts of project data. This is classified as Destructive rather than Write because the operation cannot be reversed and results in permanent data loss.

From the tool's definition Delete a campaign and all its posts. Requires confirmation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_campaign_delete 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 crow_campaign_delete, this is the rule to start with:

crow_campaign_delete Hidden

crow_campaign_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "crow_campaign_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_campaign_delete call is checked against it from then on.

FAQ

Questions about crow_campaign_delete

What does the crow_campaign_delete tool do? +

Delete a campaign and all its posts. Requires confirmation. 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.

How do I enforce a policy on crow_campaign_delete? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_campaign_delete: 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.

What risk level is crow_campaign_delete? +

crow_campaign_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit crow_campaign_delete? +

Yes. Add a rate_limit block to the crow_campaign_delete 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.

How do I block crow_campaign_delete completely? +

Set action: deny in the PolicyLayer policy for crow_campaign_delete. 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.

What MCP server provides crow_campaign_delete? +

crow_campaign_delete 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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →