Critical Risk →

delete_workflow

Delete a workflow from n8n

How to control delete_workflow ↓

What delete_workflow does on n8n MCP Server

AI agents call delete_workflow 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_workflow needs a policy

Deleting a workflow is a destructive action that cannot be undone. Once deleted, the workflow is permanently removed from n8n, and any associated configurations, execution history, or automation logic tied to that workflow is lost.

From the tool's definition Tool name is 'delete_workflow' and description states 'Delete a workflow from n8n'. The verb 'delete' combined with the action of removing a workflow represents an irreversible operation.

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

How to control delete_workflow

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_workflow:

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

delete_workflow 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_workflow

What does the delete_workflow tool do? +

Delete a workflow 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_workflow? +

Register the n8n MCP Server MCP server in PolicyLayer and add a rule for delete_workflow: 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_workflow? +

delete_workflow 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_workflow? +

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

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

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

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.