Delete a tag
AI agents call tag_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.
The tool performs a delete operation that removes data without ability to undo. While the blast radius is limited to tag metadata (not workflows or critical data), deletion is inherently destructive.
From the tool's definition Tool name 'tag_delete' with description 'Delete a tag' indicates irreversible deletion of a tag object.
Attacks that exploit this kind of access
Delete a tag. 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 tag_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.
tag_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 tag_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 tag_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.
tag_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 →