delete_member

A destructive tool on the Mailchimp MCP server.

SERVERMailchimp MCP SOURCEdamientilman/mailchimp-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/damientilman-mailchimp-mcp-server/delete-member.md

WHAT IT DOES

What delete_member does on Mailchimp MCP

AI agents call delete_member 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.

RISK

Why delete_member is rated Critical

This tool permanently removes a member (subscriber/contact) from a Mailchimp audience, which cannot be undone without manual restoration or re-import. While not financial in itself, deletion of subscriber data represents a high-severity destructive action that could cause significant business impact if triggered inappropriately.

From the tool's definition Tool name is 'delete_member' with no description provided. The verb 'delete' combined with the object 'member' indicates irreversible removal of contact data from the Mailchimp audience.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_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 delete_member, this is the rule to start with:

delete_member Hidden

delete_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_member"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every delete_member call is checked against it from then on.

FAQ

Questions about delete_member

What does the delete_member tool do? +

delete_member 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.

How do I enforce a policy on delete_member? +

Register the Mailchimp MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_member? +

delete_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_member? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_member completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_member? +

delete_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.

KEEP EXPLORING

More on Mailchimp, and thousands of servers like it.

This server

All 227 Mailchimp tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →