Delete a variable
AI agents call variable_delete to permanently remove resources in N8n Fabric — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Variables in n8n workflows are data storage entities that may be referenced by multiple workflows. Deleting a variable irreversibly removes it and could break dependent workflows or automation processes that rely on that variable. This is an irreversible data removal operation, making it Destructive rather than Write. High severity reflects the potential for workflow disruption across the automation ecosystem.
From the tool's definition Tool name is 'variable_delete' with description 'Delete a variable'. The verb 'delete' combined with the action of removing a variable is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a variable. It is categorised as a Destructive tool in the N8n Fabric MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N8n Fabric MCP server in PolicyLayer and add a rule for variable_delete: 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 Fabric. Nothing to install.
variable_delete 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 variable_delete 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 variable_delete. 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.
variable_delete is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). 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 →