Critical Risk →

delete_mailing_list

Delete a mailing list.

How to control delete_mailing_list ↓

AI agents call delete_mailing_list to permanently remove resources in Listmonk MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting a mailing list is an irreversible operation that destroys data (the list itself and likely associated subscribers, campaign history, and configurations). This cannot be undone without restoration from backups.

From the tool's definition Tool name is 'delete_mailing_list' and description states 'Delete a mailing list.' The verb 'delete' combined with operating on a mailing list constitutes irreversible data destruction.

Documented attack patterns abuse exactly the kind of access delete_mailing_list gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Listmonk MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_mailing_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_mailing_list"
  ]
}

delete_mailing_list disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Listmonk MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_mailing_list tool do? +

Delete a mailing list. It is categorised as a Destructive tool in the Listmonk MCP Server 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_mailing_list? +

Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for delete_mailing_list: 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 Listmonk MCP Server. Nothing to install.

What risk level is delete_mailing_list? +

delete_mailing_list 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_mailing_list? +

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

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

delete_mailing_list is provided by the Listmonk MCP Server MCP server (rhnvrm/listmonk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Listmonk MCP Server tool call.

Deterministic rules across all 29 Listmonk MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

29 Listmonk MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.