Critical Risk →

delete_tag

Remove unused tags from the system

How to control delete_tag ↓

What delete_tag does on n8n Workflow Builder MCP Server

AI agents call delete_tag to permanently remove resources in n8n Workflow Builder MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_tag needs a policy

This tool performs an irreversible deletion operation on tags within the n8n system. Although tags are typically low-criticality metadata compared to workflows or credentials, the deletion cannot be undone and represents a destructive action. Severity is medium rather than high/critical because tag deletion has limited blast radius—it does not directly impact workflow execution, data integrity, or credentials.

From the tool's definition Tool name 'delete_tag' and description 'Remove unused tags from the system' indicate irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access delete_tag gives an agent:

How to control delete_tag

PolicyLayer is an MCP gateway — it sits between your AI agents and n8n Workflow Builder MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_tag:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_tag"
  ]
}

delete_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register n8n Workflow Builder MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_tag

What does the delete_tag tool do? +

Remove unused tags from the system. It is categorised as a Destructive tool in the n8n Workflow Builder MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_tag? +

Register the n8n Workflow Builder MCP Server MCP server in PolicyLayer and add a rule for 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 Workflow Builder MCP Server. Nothing to install.

What risk level is delete_tag? +

delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_tag? +

Yes. Add a rate_limit block to the 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.

How do I block delete_tag completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete_tag? +

delete_tag is provided by the n8n Workflow Builder MCP Server MCP server (makafeli/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every n8n Workflow Builder MCP Server tool call.

Start from n8n Workflow Builder MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

34 n8n Workflow Builder MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.