Retry a failed run, resuming from the step that failed. Completed steps are memoized and NOT re-executed — the run picks up where it left off. Use this after a transient failure (network blip, rate limit) where you want to preserve prior progress. For a clean re-execution that runs every step fro...
Bulk/mass operation — affects multiple targets
Part of the Flowforge MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke flowforge_retry_run to trigger processes or run actions in Flowforge. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
flowforge_retry_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
flowforge_retry_run:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Flowforge policy for all 49 tools.
Agents calling execute-class tools like flowforge_retry_run have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
flowforge_retry_run is one of the high-risk operations in Flowforge. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Retry a failed run, resuming from the step that failed. Completed steps are memoized and NOT re-executed — the run picks up where it left off. Use this after a transient failure (network blip, rate limit) where you want to preserve prior progress. For a clean re-execution that runs every step from scratch (e.g. after fixing the function's code), use flowforge_replay_run instead.. It is categorised as a Execute tool in the Flowforge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for flowforge_retry_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Flowforge MCP server.
flowforge_retry_run 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 flowforge_retry_run rule in your Intercept 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 Intercept policy for flowforge_retry_run. 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.
flowforge_retry_run is provided by the Flowforge MCP server (flowforge-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept