Delete an n8n workflow by ID.
AI agents call delete_workflow to permanently remove resources in N8n Workflow Tester Safe — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a workflow is a destructive operation that cannot be undone. The workflow and its associated execution history or configurations may be permanently lost. While the blast radius is limited to the scope of a single workflow (not system-wide), the irreversibility and loss of data justifies 'high' severity in a testing/development context where workflows may represent important automation logic.
From the tool's definition Tool name is 'delete_workflow' and description states 'Delete an n8n workflow by ID.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an n8n workflow by ID. It is categorised as a Destructive tool in the N8n Workflow Tester Safe MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N8n Workflow Tester Safe 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 Tester Safe. Nothing to install.
delete_workflow 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_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.
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.
delete_workflow is provided by the N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →