AI agents invoke stop_execution to trigger actions in 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 an external operation (stopping an n8n workflow execution) whose effects depend on which execution is targeted. While it doesn't create, modify, or delete data permanently, it actively interrupts running automation processes, which constitutes an Execute action.
From the tool's definition The tool 'stop_execution' is designed to stop a running execution in n8n workflows. It requires write_mode, indicating it performs state-changing operations that affect active processes.
Attacks that exploit this kind of access
Stop a running execution. Requires write_mode. It is categorised as a Execute tool in the N8n MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the N8n MCP server in PolicyLayer and add a rule for stop_execution: 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. Nothing to install.
stop_execution 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 stop_execution 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 stop_execution. 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.
stop_execution is provided by the N8n MCP server (siddharth0903/n8n-mcp). 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 →