n8n_execute_workflow · n8n Management MCP Server MCP

WHAT IT DOES

What n8n_execute_workflow does on n8n Management MCP Server

AI agents invoke n8n_execute_workflow to trigger actions in n8n Management MCP Server. 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 n8n_execute_workflow needs a policy

This tool executes user-defined workflows with optional input data. Workflows in n8n are arbitrary automation sequences that can perform any action (API calls, database operations, file manipulation, external system invocations, etc.). The severity is high because misuse could trigger unintended workflow executions with unpredictable side effects depending on the workflow's actual implementation.

From the tool's definition Tool description states 'Manually trigger workflow execution' and 'trigger workflow execution' — the tool runs workflows, which are composed of arbitrary user-defined operations (automation sequences that may interact with external systems, databases, APIs,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

n8n_execute_workflow Rate-limited

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

FAQ

Questions about n8n_execute_workflow

What does the n8n_execute_workflow tool do? +

Manually trigger workflow execution with optional input data. Useful for testing or API-driven workflows without webhooks. Returns execution ID to track progress. Does not require workflow to be active. It is categorised as a Execute tool in the n8n Management MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on n8n_execute_workflow? +

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

What risk level is n8n_execute_workflow? +

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

Can I rate-limit n8n_execute_workflow? +

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

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

n8n_execute_workflow is provided by the n8n Management MCP Server MCP server (node2flow-th/n8n-management-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.