execute_workflow · n8n Workflow Builder MCP: Risk & Policy

WHAT IT DOES

What execute_workflow does on n8n Workflow Builder

AI agents invoke execute_workflow to trigger actions in n8n Workflow Builder. 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 execute_workflow needs a policy

This tool triggers execution of potentially complex automation logic with side effects that depend entirely on workflow content and input data. While not inherently destructive (workflows may be read-only queries), the blast radius is high because: (1) workflows can integrate with external systems, (2) execution effects are not reversible if the workflow contains write/delete operations, (3) an AI agent could…

From the tool's definition Tool name 'execute_workflow' combined with description '▶️ Execute a workflow with optional input data' indicates active execution of code/logic. The ▶️ play symbol reinforces execution semantics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_workflow Rate-limited

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

FAQ

Questions about execute_workflow

What does the execute_workflow tool do? +

▶️ Execute a workflow with optional input data. It is categorised as a Execute tool in the n8n Workflow Builder MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_workflow? +

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

What risk level is execute_workflow? +

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

Can I rate-limit execute_workflow? +

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

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

execute_workflow is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.