workflow_execute · N8n Fabric MCP: Risk & Policy

WHAT IT DOES

What workflow_execute does on N8n Fabric

AI agents invoke workflow_execute to trigger actions in N8n Fabric. 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 workflow_execute needs a policy

This tool runs code/workflows whose effects depend entirely on what the workflow contains. The n8n server integrates with other tools and external systems, meaning a workflow execution could read data, modify systems, make API calls, or trigger other operations. This is clearly an Execute category tool.

From the tool's definition Tool name is 'workflow_execute' and description states 'Execute a workflow manually with optional input data'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

workflow_execute Rate-limited

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

FAQ

Questions about workflow_execute

What does the workflow_execute tool do? +

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

How do I enforce a policy on workflow_execute? +

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

What risk level is workflow_execute? +

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

Can I rate-limit workflow_execute? +

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

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

workflow_execute is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.