Trigger immediate execution of a workflow by its ID. Starts the workflow manually regardless of its normal triggers (webhooks, schedules, etc.). Returns execution details including status, start time, and any immediate results or errors.
AI agents invoke execute_workflow to trigger actions in n8n Workflow Builder 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.
This tool runs code/operations whose effects depend entirely on the workflow configuration (unknown argument-dependent side effects). A workflow could perform any action—write to databases, make API calls, send emails, etc. While the tool itself doesn't delete or move money directly, it invokes arbitrary workflow logic that could have severe consequences if misconfigured or abused by an AI agent.
From the tool's definition Tool description states it 'Trigger[s] immediate execution of a workflow' and 'Starts the workflow manually'. The term 'execute' combined with triggering external operations (running workflows) matches the Execute category definition.
Documented attack patterns abuse exactly the kind of access execute_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and n8n Workflow Builder MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"execute_workflow": {
"limits": [
{
"counter": "execute_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Trigger immediate execution of a workflow by its ID. Starts the workflow manually regardless of its normal triggers (webhooks, schedules, etc.). Returns execution details including status, start time, and any immediate results or errors. It is categorised as a Execute tool in the n8n Workflow Builder MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the n8n Workflow Builder MCP Server 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 MCP Server. Nothing to install.
execute_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
execute_workflow is provided by the n8n Workflow Builder MCP Server MCP server (makafeli/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from n8n Workflow Builder MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 n8n Workflow Builder MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.