Delete a campaign permanently. This cannot be undone.
AI agents call delete_campaign to permanently remove resources in DM20 Protocol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a campaign) with no recovery mechanism. While the blast radius is limited to game data within a specific campaign rather than production systems or financial data, the permanent loss of user-created content (campaign details, characters, sessions, world-building) represents a destructive action.
From the tool's definition Tool name is 'delete_campaign' and description explicitly states 'Delete a campaign permanently. This cannot be undone.' The use of 'permanently' and 'cannot be undone' are defining characteristics of destructive operations.
Attacks that exploit this kind of access
Delete a campaign permanently. This cannot be undone. It is categorised as a Destructive tool in the DM20 Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for delete_campaign: 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 DM20 Protocol. Nothing to install.
delete_campaign 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 delete_campaign 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 delete_campaign. 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.
delete_campaign is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). 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 →