n8n_update_tag · n8n MCP Server MCP: Risk & Policy

WHAT IT DOES

What n8n_update_tag does on n8n MCP Server

AI agents use n8n_update_tag to create or update resources in n8n MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n MCP Server environment.

WHY IT NEEDS A POLICY

Why n8n_update_tag needs a policy

This tool creates a modification to stored metadata (tag naming) without destructive consequences. Renaming is a classic Write operation: it alters state but remains fully reversible and has minimal blast radius. An LLM agent misusing this tool could only rename tags within the n8n instance, causing organizational confusion but no data loss or external impact.

From the tool's definition The tool description states it will "Rename an existing tag," which modifies existing data (the tag's name attribute). The operation is reversible—the tag can be renamed again to its original or any other name.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_update_tag Rate-limited

n8n_update_tag stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "n8n_update_tag": {
      "limits": [
        {
          "counter": "n8n_update_tag_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches n8n MCP Server, so you can run agents against it safely.

FAQ

Questions about n8n_update_tag

What does the n8n_update_tag tool do? +

Rename an existing tag. Args: - id (string): Tag ID - name (string): New tag name. It is categorised as a Write tool in the n8n MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on n8n_update_tag? +

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

What risk level is n8n_update_tag? +

n8n_update_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit n8n_update_tag? +

Yes. Add a rate_limit block to the n8n_update_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 n8n_update_tag completely? +

Set action: deny in the PolicyLayer policy for n8n_update_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 n8n_update_tag? +

n8n_update_tag is provided by the n8n MCP Server MCP server (verzth/mcp-n8n). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.