MCP Tool Reference Low Risk

rerun_workflow

Rerun workflow from start or from failed job

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

CircleCI-Public/mcp-server-circleci Other

WHEN AI AGENTS USE THIS TOOL

AI agents call rerun_workflow to perform operations in CircleCI. While the risk category is not fully classified, applying a rate limit gives you visibility into how often the tool is called and prevents unexpected bursts of activity from autonomous agents.

WHY ENFORCE A POLICY ON RERUN_WORKFLOW

Applying a policy to rerun_workflow gives you an audit trail of every call an AI agent makes. Even for low-risk tools, visibility into agent behaviour helps you debug issues, optimise workflows, and maintain compliance with your organisation's security requirements.

RECOMMENDED POLICY

Apply a rate limit to control usage and monitor for unexpected behaviour.

circleci.yaml 
tools:
  rerun_workflow:
    rules:
      - action: allow
        rate_limit:
          max: 60
          window: 60

See the full CircleCI policy for all 15 tools.

DETAILS

Tool Name

rerun_workflow

Category

Other

MCP Server

CircleCI MCP Server

Risk Level

Low

MORE CIRCLECI TOOLS

analyse_diff Other
Analyse git diffs against cursor rules for violations
config_helper Other
Validate and get guidance for CircleCI configuration
download_usage_api_data Other
Download usage data from CircleCI Usage API
recommend_prompt_template_tests Other
Generate test cases for prompt templates
find_flaky_tests Read
Identify flaky tests by analysing test execution history
find_underused_resource_classes Read
Find jobs with underused compute resources
get_build_failure_logs Read
Retrieve detailed failure logs from builds
get_job_test_results Read
Retrieve test metadata and results for jobs

View all 15 tools →

SIMILAR OTHER TOOLS ON OTHER SERVERS

analytics Algolia
Access Algolia analytics data
monitoring Algolia
Monitor Algolia service status
recommend Algolia
Access Algolia recommendation features
abtesting Algolia
Manage A/B tests
collections Algolia
Manage query suggestions collections
usage Algolia
Access Algolia usage data

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the rerun_workflow tool do?

Rerun workflow from start or from failed job. It is categorised as a Other tool in the CircleCI MCP Server, which means it performs auxiliary operations.

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 Other tool with low risk. Read-only tools are generally safe to allow by default.

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.

VIEW ON GITHUB Full CircleCI policy →