Critical Risk →

delete_execution

Delete a specific workflow execution from n8n

How to control delete_execution ↓

What delete_execution does on n8n MCP Server

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

Critical Risk

Why delete_execution needs a policy

Deleting a workflow execution removes historical records that cannot be recovered. This is an irreversible operation that destroys audit trails and execution data. While not as critical as deleting entire workflows, execution deletion still represents permanent data loss.

From the tool's definition Tool name is 'delete_execution' and description states 'Delete a specific workflow execution from n8n'. The verb 'delete' indicates irreversible removal of data.

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

How to control delete_execution

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

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

delete_execution 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 n8n 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.

Related tools and policies

Go deeper

Questions about delete_execution

What does the delete_execution tool do? +

Delete a specific workflow execution from n8n. It is categorised as a Destructive tool in the n8n 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_execution? +

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

What risk level is delete_execution? +

delete_execution 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_execution? +

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

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

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

Enforce policy on every n8n MCP Server tool call.

Start from n8n MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 n8n MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.