remove_automation_subscriber
A destructive tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/remove-automation-subscriber.md
What remove_automation_subscriber does on Mailchimp MCP
AI agents call remove_automation_subscriber to permanently remove resources in Mailchimp MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_automation_subscriber is rated Critical
An AI agent that decides to call remove_automation_subscriber doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mailchimp MCP is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_automation_subscriber safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mailchimp MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_automation_subscriber, this is the rule to start with:
remove_automation_subscriber is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every remove_automation_subscriber call is checked against it from then on.
Questions about remove_automation_subscriber
remove_automation_subscriber is a destructive tool on the Mailchimp MCP server. It is categorised as a Destructive tool in the Mailchimp MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailchimp MCP server in PolicyLayer and add a rule for remove_automation_subscriber: 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. Nothing to install.
remove_automation_subscriber 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 remove_automation_subscriber 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 remove_automation_subscriber. 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.
remove_automation_subscriber is provided by the Mailchimp MCP server (damientilman/mailchimp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mailchimp, and thousands of servers like it.
Across the catalogue