High Risk →

run-rerun

Re-runs a workflow run by ID. Optionally re-runs only failed jobs or a specific job. Returns structured result with run ID, status, and URL.

Accepts file system path (path); Single-target operation

Part of the Github MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/github Execute Risk 3/5

AI agents invoke run-rerun to trigger processes or run actions in Github. 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.

run-rerun 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.

io-github-dave-london-github.yaml
tools:
  run-rerun:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Github policy for all 27 tools.

Tool Name run-rerun
Category Execute
MCP Server Github MCP Server
Risk Level High

View all 27 tools →

Agents calling execute-class tools like run-rerun have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

run-rerun is one of the high-risk operations in Github. 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.

What does the run-rerun tool do? +

Re-runs a workflow run by ID. Optionally re-runs only failed jobs or a specific job. Returns structured result with run ID, status, and URL.. It is categorised as a Execute tool in the Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run-rerun? +

Add a rule in your Intercept YAML policy under the tools section for run-rerun. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Github MCP server.

What risk level is run-rerun? +

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

Can I rate-limit run-rerun? +

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

How do I block run-rerun completely? +

Set action: deny in the Intercept policy for run-rerun. 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 run-rerun? +

run-rerun is provided by the Github MCP server (@paretools/github). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Github

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.