n8n_retry_execution

Retry a failed execution. Creates a new execution from the point of failure. Args: - id (string): Failed execution ID to retry - loadWorkflowData (boolean): Reload workflow from current saved version (default false — uses original execution data)

Server n8n MCP Server verzth/mcp-n8n
Category Execute
Risk class High
Parameters 00 required

What n8n_retry_execution does on n8n MCP Server

AI agents invoke n8n_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.

Why n8n_retry_execution needs a policy

This tool triggers a new workflow execution, which is an external operation with effects that depend on the workflow being run. It does not merely read data or write a record — it actively re-runs automation logic that could have side effects (API calls, data transformations, notifications, etc.).

From the tool's definition 'Retry a failed execution. Creates a new execution from the point of failure.'

Questions about n8n_retry_execution

What does the n8n_retry_execution tool do? +

Retry a failed execution. Creates a new execution from the point of failure. Args: - id (string): Failed execution ID to retry - loadWorkflowData (boolean): Reload workflow from current saved version (default false — uses original execution data). 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.

How do I enforce a policy on n8n_retry_execution? +

Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_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.

What risk level is n8n_retry_execution? +

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

Can I rate-limit n8n_retry_execution? +

Yes. Add a rate_limit block to the n8n_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.

How do I block n8n_retry_execution completely? +

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

What MCP server provides n8n_retry_execution? +

n8n_retry_execution is provided by the n8n MCP Server MCP server (verzth/mcp-n8n). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.