n8n_create_workflow · n8n- MCP: Risk & Policy

WHAT IT DOES

What n8n_create_workflow does on n8n-MCP

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

WHY IT NEEDS A POLICY

Why n8n_create_workflow needs a policy

This tool creates new workflows in n8n, which are persistent configurations that can orchestrate external systems and data. While not destructive (workflows can be deleted) or financial, creating workflows is a Write operation that modifies system state. The severity is high because a malicious agent could create workflows that access sensitive integrations, extract data, or trigger unintended business processes.

From the tool's definition Tool creates a new workflow with name, nodes, and connections. Description states 'Create workflow' and 'Returns workflow with ID', indicating persistent data creation in the n8n system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_create_workflow Rate-limited

n8n_create_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": {
    "n8n_create_workflow": {
      "limits": [
        {
          "counter": "n8n_create_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-MCP, so you can run agents against it safely.

FAQ

Questions about n8n_create_workflow

What does the n8n_create_workflow tool do? +

Create workflow. Requires: name, nodes[], connections{}. Created inactive. Returns workflow with ID. It is categorised as a Write tool in the n8n-MCP 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_create_workflow? +

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

What risk level is n8n_create_workflow? +

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

Can I rate-limit n8n_create_workflow? +

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

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

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