AI agents invoke n8n_execute_workflow to trigger actions in Mcp 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.
This tool triggers execution of automation workflows whose actual effects depend entirely on what the workflow contains. The user/agent provides only the workflow ID and optional input data, but cannot control what the workflow does once executed.
From the tool's definition Tool name explicitly states 'execute' and description confirms it 'Execute a workflow manually with optional input data.' Workflows in n8n are automation sequences that can perform arbitrary operations including API calls, data modifications, file operations,…
Attacks that exploit this kind of access
Execute a workflow manually with optional input data. It is categorised as a Execute tool in the Mcp N8n MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp N8n 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 Mcp N8n. Nothing to install.
n8n_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 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.
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.
n8n_execute_workflow is provided by the Mcp N8n MCP server (lyzetam/mcp-n8n). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →