Delete a specific workflow execution from n8n
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.
This tool irreversibly deletes workflow execution records, which cannot be undone. While the blast radius is limited to execution history rather than live workflows or data, deletion of audit/execution logs is destructive and could impact compliance, debugging, and system accountability. Severity is high rather than critical because it affects execution metadata rather than production data or workflows themselves.
From the tool's definition Tool name is 'delete_execution' and description states 'Delete a specific workflow execution from n8n'. The verb 'delete' combined with the action of removing execution records is irreversible.
Documented attack patterns abuse exactly the kind of access delete_execution gives an agent:
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:
{
"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.
Free to start. No card required.
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.
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.
delete_execution 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_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.
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.
delete_execution is provided by the n8n MCP Server MCP server (jacob-dietle/n8n-mcp-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.