AI agents use mailchimp_add_member to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Subscriber email address |
status | string | — | Subscription status (default: subscribed) |
api_key | string | Yes | Mailchimp API key |
list_id | string | Yes | Audience ID |
last_name | string | — | Subscriber last name |
first_name | string | — | Subscriber first name |
Parameters from the server's own tool schema.
This tool creates or modifies subscriber records in Mailchimp (a marketing automation platform). While the operations are reversible (subscribers can be removed, data updated), the action materially changes business data. The blast radius is moderate: an AI agent could spam audiences, add invalid records, or corrupt subscriber lists, but the impact is limited to a single audience and can be undone.
From the tool's definition Tool description states 'Add or update a subscriber in a Mailchimp audience' — direct modification of audience data through reversible create/update operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Add or update a subscriber in a Mailchimp audience. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mailchimp_add_member accepts 6 parameters: email, status, api_key, list_id, last_name, first_name. Required: email, api_key, list_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mailchimp_add_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 UnClick. Nothing to install.
mailchimp_add_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 mailchimp_add_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 mailchimp_add_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.
mailchimp_add_member is provided by the UnClick MCP server (@unclick/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 →