campaign_delete
AI agents call campaign_delete to permanently remove resources in Task Crusader MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' verb in the tool name indicates data destruction. In a campaign/project management context, deleting a campaign would irreversibly remove associated tasks, dependencies, acceptance criteria, and progress tracking—data that cannot be recovered. While the empty description reduces confidence slightly, the semantic meaning of 'delete' in this domain clearly maps to the Destructive category.
From the tool's definition Tool name 'campaign_delete' combined with context of a task/campaign management system indicates irreversible deletion of campaign data. The sibling tools show this server manages projects, tasks, dependencies, and progress—all valuable project state.
Attacks that exploit this kind of access
campaign_delete. It is categorised as a Destructive tool in the Task Crusader MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Task Crusader MCP server in PolicyLayer and add a rule for 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 Task Crusader MCP. Nothing to install.
campaign_delete 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 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.
Set action: deny in the PolicyLayer policy for 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.
campaign_delete is provided by the Task Crusader MCP server (mcrescenzo/task-crusader-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →