add_node_to_workflow · N8n Workflow Tester Safe MCP

WHAT IT DOES

What add_node_to_workflow does on N8n Workflow Tester Safe

AI agents use add_node_to_workflow to create or update resources in N8n Workflow Tester Safe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N8n Workflow Tester Safe environment.

WHY IT NEEDS A POLICY

Why add_node_to_workflow needs a policy

This tool modifies workflow state by adding a new node, which is a reversible change (the node can be removed). It does not execute the workflow, delete data, or move funds. The medium severity reflects that malicious node additions could alter workflow behavior in unintended ways, but the change is reversible and the server's safety-first design (no credential/secrets management) limits blast radius.

From the tool's definition Tool description states it will 'Append a node JSON object to an existing workflow' — this is a modification operation that creates or alters workflow configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_node_to_workflow Rate-limited

add_node_to_workflow 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": {
    "add_node_to_workflow": {
      "limits": [
        {
          "counter": "add_node_to_workflow_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 Workflow Tester Safe, so you can run agents against it safely.

FAQ

Questions about add_node_to_workflow

What does the add_node_to_workflow tool do? +

Append a node JSON object to an existing workflow. It is categorised as a Write tool in the N8n Workflow Tester Safe 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_to_workflow? +

Register the N8n Workflow Tester Safe MCP server in PolicyLayer and add a rule for add_node_to_workflow: 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 Tester Safe. Nothing to install.

What risk level is add_node_to_workflow? +

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

Can I rate-limit add_node_to_workflow? +

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

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

add_node_to_workflow is provided by the N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.