pause_automation
AI agents invoke pause_automation to trigger actions in Mailchimp MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pausing an automation triggers an external operational state change in Mailchimp — it stops an active automation workflow, which affects outgoing emails and scheduled sequences. This is not a simple read or write of data; it executes a control action on a running process. The description is empty, so confidence is reduced, but the name strongly implies an operational trigger.
From the tool's definition Tool name 'pause_automation' on a Mailchimp MCP server that manages automations. Description is empty and uninformative.
Attacks that exploit this kind of access
pause_automation. It is categorised as a Execute tool in the Mailchimp MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mailchimp MCP Server MCP server in PolicyLayer and add a rule for pause_automation: 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.
pause_automation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pause_automation 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 pause_automation. 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.
pause_automation 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 →