New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_store

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-store.md

What delete_store does on Mailchimp MCP

AI agents call delete_store 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_store is rated Critical

The 'delete' verb combined with 'store' (a data container in e-commerce contexts) indicates an irreversible data destruction action. Even without explicit confirmation in the description, this falls into the Destructive category as it cannot be undone by normal means and would result in loss of store data and potentially associated customer/order information.

From the tool's definition Tool name 'delete_store' strongly indicates irreversible deletion of a store entity. Context is Mailchimp MCP with e-commerce capabilities (sibling tool 'create_account_export' suggests store management).

Questions about delete_store

What does the delete_store tool do? +

delete_store 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_store? +

Register the Mailchimp MCP server in PolicyLayer and add a rule for delete_store: 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_store? +

delete_store 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_store? +

Yes. Add a rate_limit block to the delete_store 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_store completely? +

Set action: deny in the PolicyLayer policy for delete_store. 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_store? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mailchimp's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.