Delete an execution from the history. Requires write_mode.
AI agents call delete_execution to permanently remove resources in N8n — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting execution history records is irreversible data destruction. While not as critical as deleting workflows or credentials themselves, execution history is often required for auditing, compliance, debugging, and forensic analysis. An agent misusing this tool could destroy evidence of workflow runs, making it impossible to trace what happened in automation processes.
From the tool's definition Tool description states 'Delete an execution from the history' - the verb 'delete' combined with 'from the history' indicates irreversible removal of data. This is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete an execution from the history. Requires write_mode. It is categorised as a Destructive tool in the N8n MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N8n 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. 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 (siddharth0903/n8n-mcp). 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 →