get_tag · n8n Workflow Builder MCP Server MCP: Risk & Policy

WHAT IT DOES

What get_tag does on n8n Workflow Builder MCP Server

AI agents call get_tag to retrieve information from n8n Workflow Builder MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_tag needs a policy

This tool retrieves metadata about a tag in n8n workflows by ID. It performs a straightforward data lookup with no capability to modify, delete, or execute operations. The retrieval of tag details is a non-destructive read operation that poses minimal risk even if invoked by an AI agent.

From the tool's definition Tool name 'get_tag' and description 'Retrieve individual tag details by ID' indicate a read-only query operation with no side effects.

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

POLICY

How to control get_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 get_tag:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tag": {}
  }
}

get_tag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More n8n Workflow Builder MCP Server tools

Destructive delete_credential Delete a credential by ID. This will remove the credential and make it unavailable for wor Destructive delete_execution Delete a workflow execution record from the n8n instance Destructive delete_tag Remove unused tags from the system Destructive delete_workflow Delete an n8n workflow Destructive remove_node Remove a node from a workflow (also removes its connections) Execute execute_workflow Trigger immediate execution of a workflow by its ID. Starts the workflow manually regardle Execute activate_workflow Activate an n8n workflow Execute create_workflow_and_activate Create and activate an n8n workflow

All 34 n8n Workflow Builder MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_tag

What does the get_tag tool do? +

Retrieve individual tag details by ID. It is categorised as a Read tool in the n8n Workflow Builder MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tag? +

Register the n8n Workflow Builder MCP Server MCP server in PolicyLayer and add a rule for get_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 get_tag? +

get_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tag? +

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

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

get_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.

CHECK YOUR STACK →

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.