add_node · n8n Workflow Builder MCP Server MCP

WHAT IT DOES

What add_node does on n8n Workflow Builder MCP Server

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

THE RISK

Medium Risk

Why add_node needs a policy

This tool creates/modifies workflow configuration by adding nodes, which is reversible (nodes can be removed). It does not execute code directly, delete data irreversibly, or move money, so it is Write rather than Execute or Destructive.

From the tool's definition Tool description states 'Add a single node to an existing workflow', indicating creation of a new workflow component.

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

POLICY

How to control add_node

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 add_node:

policy.json

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

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

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.

LIMIT 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_node

What does the add_node tool do? +

Add a single node to an existing workflow. It is categorised as a Write tool in the n8n Workflow Builder 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 add_node? +

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

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

Can I rate-limit add_node? +

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

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

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