create_and_validate_workflow · N8n MCP: Risk & Policy

WHAT IT DOES

What create_and_validate_workflow does on N8n

AI agents invoke create_and_validate_workflow to trigger actions in N8n. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_and_validate_workflow needs a policy

Because the tool triggers actual executions of the newly created workflow during validation, it crosses from Write into Execute territory. The blast radius is high: an AI agent could create and immediately run arbitrary automation workflows with unintended side effects on connected systems.

From the tool's definition 'Create a workflow with automatic double-validation: structural check, two execution' — the tool not only creates a workflow (Write) but also executes it ('two execution') as part of the validation process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_and_validate_workflow Rate-limited

create_and_validate_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_and_validate_workflow": {
      "limits": [
        {
          "counter": "create_and_validate_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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, so you can run agents against it safely.

FAQ

Questions about create_and_validate_workflow

What does the create_and_validate_workflow tool do? +

Create a workflow with automatic double-validation: structural check, two execution. It is categorised as a Execute tool in the N8n MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_and_validate_workflow? +

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

What risk level is create_and_validate_workflow? +

create_and_validate_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_and_validate_workflow? +

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

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

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