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.

SERVERGit SOURCEDave-London/Pare
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/run-rerun.md

What run-rerun does on Git

AI agents invoke run-rerun to trigger actions in Git. 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 run-rerun is rated High

This tool executes a workflow/CI pipeline, which is an external operation with side effects that depend on user-supplied arguments (the run ID and optional job filters). While the effects are typically reversible (workflows can be cancelled or re-run), the execution of potentially arbitrary pipeline logic qualifies as Execute rather than Write.

From the tool's definition "Re-runs a workflow run by ID" indicates triggering external CI/CD operations whose effects depend on the run ID argument provided.

Questions about run-rerun

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 Git 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? +

Register the Git MCP server in PolicyLayer and add a rule for run-rerun: 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 Git. Nothing to install.

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 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 run-rerun completely? +

Set action: deny in the PolicyLayer 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 Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Git, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Git's. Pull the full record:

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.