Delete an instance variable. Requires write_mode.
AI agents call delete_variable 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.
This tool permanently removes an instance variable from the n8n workflow system. Deletion is irreversible—once a variable is deleted, its data is lost unless backed up externally. An AI agent misusing this tool could destroy critical workflow state or configuration data that other workflows depend on, disrupting automation processes.
From the tool's definition Tool name is 'delete_variable' and description states 'Delete an instance variable.' The verb 'delete' combined with the action of removing a variable irreversibly qualifies this as a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete an instance variable. 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_variable: 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_variable 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_variable 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_variable. 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_variable 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 →