delete_segment
A destructive tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/delete-segment.md
What delete_segment does on Mailchimp MCP
AI agents call delete_segment 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.
Why delete_segment is rated Critical
Segment deletion cannot be undone and represents permanent loss of audience grouping configuration. While not directly affecting contacts themselves, segments are structural data whose removal has lasting consequences. Confidence is 0.85 rather than higher due to the empty description, which prevents verification of exact behavior and scope.
From the tool's definition Tool name is 'delete_segment' with empty description. The 'delete' verb indicates irreversible removal of data (a segment in Mailchimp).
Attacks that exploit this kind of access
The rule that runs delete_segment 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_segment, this is the rule to start with:
delete_segment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every delete_segment call is checked against it from then on.
Questions about delete_segment
delete_segment 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.
Register the Mailchimp MCP server in PolicyLayer and add a rule for delete_segment: 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.
delete_segment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_segment 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 delete_segment. 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.
delete_segment 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.
Across the catalogue