unsubscribe_member
A write tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/unsubscribe-member.md
What unsubscribe_member does on Mailchimp MCP
AI agents use unsubscribe_member to create or update resources in Mailchimp MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailchimp MCP environment.
Why unsubscribe_member is rated Medium
Based on the name, this tool likely changes a member's subscription status to unsubscribed in Mailchimp. This is a Write operation (modifying a member's status), but it could have significant impact as it affects communication preferences and marketing lists.
From the tool's definition Tool name 'unsubscribe_member' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs unsubscribe_member 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 unsubscribe_member, this is the rule to start with:
unsubscribe_member stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every unsubscribe_member call is checked against it from then on.
Questions about unsubscribe_member
unsubscribe_member is a write tool on the Mailchimp MCP server. It is categorised as a Write tool in the Mailchimp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailchimp MCP server in PolicyLayer and add a rule for unsubscribe_member: 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.
unsubscribe_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unsubscribe_member 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 unsubscribe_member. 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.
unsubscribe_member 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.
This server
Across the catalogue