delete_campaign
AI agents call delete_campaign to permanently remove resources in Mailchimp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of campaigns is a destructive operation that permanently removes marketing data and cannot be undone. This poses a high risk if an AI agent mistakenly deletes important campaigns. While the description is empty, the tool name unambiguously indicates a destructive action, and the severity reflects the irreversible loss of potentially valuable marketing assets.
From the tool's definition Tool name 'delete_campaign' directly indicates deletion of a campaign. Mailchimp campaigns are marketing assets that, once deleted, cannot be recovered. The action is irreversible.
Attacks that exploit this kind of access
delete_campaign. It is categorised as a Destructive tool in the Mailchimp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailchimp MCP Server 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 Mailchimp MCP Server. 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 Mailchimp MCP Server MCP server (mattcoatsworth/mailchip-mcp-server). 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 →