add_list_member
AI agents use add_list_member to create or update resources in Mailchimp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailchimp MCP Server environment.
The tool adds a member to an email list, which creates or modifies data reversibly. This is a Write operation—it can be undone by removing the member. While the empty description limits confidence slightly, the function name is clear. Severity is medium because bulk misuse could spam contacts or compromise list integrity, but individual additions are generally reversible and non-destructive.
From the tool's definition Tool name 'add_list_member' indicates adding/modifying membership in a Mailchimp list. Context from sibling tools ('create_campaign', 'create_list', 'create_template') confirms this server performs write operations.
Attacks that exploit this kind of access
add_list_member. It is categorised as a Write tool in the Mailchimp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailchimp MCP Server MCP server in PolicyLayer and add a rule for add_list_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 Server. Nothing to install.
add_list_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 add_list_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 add_list_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.
add_list_member 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 →