High Risk →

rerun_workflow

Rerun workflow from start or failed job

Re-triggers CI/CD workflow execution

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

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

rerun_workflow 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.

circleci.yaml
tools:
  rerun_workflow:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full CircleCI policy for all 15 tools.

Tool Name rerun_workflow
Category Execute
MCP Server CircleCI MCP Server
Risk Level High

View all 15 tools →

Agents calling execute-class tools like rerun_workflow 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.

rerun_workflow is one of the high-risk operations in CircleCI. 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 rerun_workflow tool do? +

Rerun workflow from start or failed job. It is categorised as a Execute tool in the CircleCI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rerun_workflow? +

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

What risk level is rerun_workflow? +

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

Can I rate-limit rerun_workflow? +

Yes. Add a rate_limit block to the rerun_workflow 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 rerun_workflow completely? +

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

rerun_workflow is provided by the CircleCI MCP server (@CircleCI-Public/mcp-server-circleci). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on CircleCI

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.