delete_workflow
Hapus workflow dari n8n secara permanen.
This record as markdown: /tools/andhit-r-n8n-mcp/delete-workflow.md
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.
Why delete_workflow is rated Critical
This tool permanently deletes a workflow, which cannot be undone. Deletion is irreversible data destruction, fitting the Destructive category. Severity is high because losing a workflow could disrupt business processes, though it does not directly affect financial systems or involve code execution. Confidence is high due to explicit 'permanent' language in the description.
From the tool's definition Tool description states 'Hapus workflow dari n8n secara permanen' (Delete workflow from n8n permanently). The word 'permanen' (permanent) and the tool name 'delete_workflow' indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and n8n MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_workflow, this is the rule to start with:
delete_workflow is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect n8n MCP Server, apply this rule, and every delete_workflow call is checked against it from then on.
Questions about delete_workflow
Hapus workflow dari n8n secara permanen. 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_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.
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 MCP Server MCP server (andhit-r/n8n-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on n8n MCP Server, and thousands of servers like it.
Across the catalogue