delete_template
AI agents call delete_template 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.
The 'delete_template' function removes data that cannot be recovered. This is a destructive operation that permanently eliminates a template from the Mailchimp system. While the description is empty, the tool name leaves no ambiguity about the destructive nature of this action. Given the marketing context, a deleted template could disrupt active campaigns or automations.
From the tool's definition Tool name 'delete_template' explicitly indicates permanent deletion. The server manages email marketing templates, and deletion is irreversible.
Attacks that exploit this kind of access
delete_template. 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_template: 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_template 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_template 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_template. 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_template 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 →