delete_workflow

🗑️ Delete (archive) a workflow. This removes the workflow from n8n.

Server n8n Workflow Builder schimmilab/n8n-workflow-builder
Category Destructive
Risk class Critical
Parameters 00 required

What delete_workflow does on n8n Workflow Builder

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

Why delete_workflow needs a policy

This tool permanently removes workflows from the n8n system. While described as archiving (which might suggest reversibility in some systems), the explicit use of 'delete' and 'removes' indicates an irreversible action that cannot be undone without restore operations outside the tool's scope. This qualifies as Destructive rather than Write, as it destroys rather than modifies data.

From the tool's definition Tool description explicitly states 'Delete (archive) a workflow. This removes the workflow from n8n.' The verb 'delete' paired with 'removes' indicates irreversible removal of data/configurations.

Questions about delete_workflow

What does the delete_workflow tool do? +

🗑️ Delete (archive) a workflow. This removes the workflow from n8n. It is categorised as a Destructive tool in the n8n Workflow Builder 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 Workflow Builder 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 Workflow Builder. 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 Workflow Builder MCP server (schimmilab/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.