delete_execution

THE RISK

Critical Risk

Why delete_execution needs a policy

This tool permanently removes workflow execution records, which cannot be undone. Execution records are audit trails and historical data. Deletion is irreversible and destructive, placing it above Write (which is reversible). The blast radius is high: an AI agent could erase evidence of workflow runs, audit trails, or execution history, hindering debugging and compliance.

From the tool's definition Tool name is 'delete_execution' and description states 'Delete a workflow execution record' — uses explicit 'Delete' verb indicating irreversible removal of data.

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

POLICY

How to control delete_execution

PolicyLayer is an MCP gateway — it sits between your AI agents and n8n Workflow Builder 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.

Create a free account and register n8n Workflow Builder MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More n8n Workflow Builder MCP Server tools

Destructive delete_credential Delete a credential by ID. This will remove the credential and make it unavailable for wor Destructive delete_tag Remove unused tags from the system Destructive delete_workflow Delete an n8n workflow Destructive remove_node Remove a node from a workflow (also removes its connections) Execute execute_workflow Trigger immediate execution of a workflow by its ID. Starts the workflow manually regardle Execute activate_workflow Activate an n8n workflow Execute create_workflow_and_activate Create and activate an n8n workflow Write add_node Add a single node to an existing workflow

All 34 n8n Workflow Builder MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in n8n Workflow Builder MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_execution

What does the delete_execution tool do? +

Delete a workflow execution record from the n8n instance. It is categorised as a Destructive tool in the n8n Workflow Builder 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 Workflow Builder 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 Workflow Builder 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 Workflow Builder MCP Server MCP server (makafeli/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every n8n Workflow Builder MCP Server tool call.

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

CHECK YOUR STACK →