Delete an execution
AI agents call delete_execution 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.
This tool irreversibly deletes execution records from N8N workflows. Once deleted, execution history, logs, and associated metadata cannot be recovered. In a production automation system, execution records are critical for audit trails, debugging, compliance, and operational visibility. Deletion of executions could destroy evidence of workflow behavior, financial transaction records, or compliance-related logs.
From the tool's definition Tool name 'delete_execution' with description 'Delete an execution' - the verb 'delete' combined with the action of removing workflow execution records indicates irreversible data removal.
Attacks that exploit this kind of access
Delete an execution. 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_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 MCP Server. Nothing to install.
delete_execution 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_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.
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.
delete_execution is provided by the N8N MCP Server MCP server (rajtrafficradius/n8n-mcpv2). 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 →