Remove tag from system. Automatically removes this tag from all workflows using it. Tag removal does not affect workflows themselves, only the tag association.
AI agents call n8n_delete_tag to permanently remove resources in n8n Management 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 a tag and all its associations with workflows. While the blast radius is limited (tags are metadata, workflows themselves are unaffected), the action cannot be undone and affects multiple resources. This qualifies as Destructive rather than Write because the operation is not reversible—once deleted, the tag and its associations are gone.
From the tool's definition Tool description explicitly states 'Remove tag from system' and 'Automatically removes this tag from all workflows using it.' The verb 'Remove' combined with permanent deletion of tag associations across multiple workflows indicates irreversible data removal.
Attacks that exploit this kind of access
Remove tag from system. Automatically removes this tag from all workflows using it. Tag removal does not affect workflows themselves, only the tag association. It is categorised as a Destructive tool in the n8n Management MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the n8n Management MCP Server MCP server in PolicyLayer and add a rule for n8n_delete_tag: 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 Management MCP Server. Nothing to install.
n8n_delete_tag 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 n8n_delete_tag 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 n8n_delete_tag. 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.
n8n_delete_tag is provided by the n8n Management MCP Server MCP server (node2flow-th/n8n-management-mcp-community). 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 →