Retry an execution
AI agents invoke retry_execution to trigger actions in N8N 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.
Retrying an execution re-runs a workflow, which constitutes triggering an external operation. The effects depend on what the workflow does (could involve side effects like sending emails, API calls, etc.), making this an Execute category tool. Severity is medium as it could cause duplicate operations or unintended side effects depending on the workflow being retried.
From the tool's definition 'Retry an execution' - re-triggers a workflow execution in N8N
Attacks that exploit this kind of access
Retry an execution. It is categorised as a Execute tool in the N8N MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the N8N MCP Server MCP server in PolicyLayer and add a rule for retry_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 MCP Server. Nothing to install.
retry_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 retry_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 retry_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.
retry_execution is provided by the N8N MCP Server MCP server (rajtrafficradius/n8n-mcpv2). 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 →