Critical Risk →

delete_template

Delete an email template.

How to control delete_template ↓

AI agents call delete_template 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

This tool permanently removes an email template from the Listmonk instance. Template deletion cannot be undone—the template and its data are lost. This is a classic destructive operation. While the blast radius is limited to templates (not financial or system-critical), accidental deletion of important email templates could disrupt campaigns or workflows, justifying 'high' severity.

From the tool's definition Tool name is 'delete_template' and description states 'Delete an email template.' The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_template 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_template:

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

delete_template 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_template tool do? +

Delete an email template. 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_template? +

Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for delete_template: 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_template? +

delete_template 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_template? +

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

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

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