MCP Tool Reference Low Risk

find_flaky_tests

Identify flaky tests by analysing test execution history

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

WHEN AI AGENTS USE THIS TOOL

AI agents call find_flaky_tests to retrieve information from CircleCI without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.

WHY ENFORCE A POLICY ON FIND_FLAKY_TESTS

Even though find_flaky_tests only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

circleci.yaml
tools:
  find_flaky_tests:
    rules:
      - action: allow

See the full CircleCI policy for all 15 tools.

DETAILS

Tool Name

find_flaky_tests

Category

Read

MCP Server

CircleCI MCP Server

Risk Level

Low

MORE CIRCLECI TOOLS

View all 15 tools →

SIMILAR READ TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the find_flaky_tests tool do?

Identify flaky tests by analysing test execution history. It is categorised as a Read tool in the CircleCI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_flaky_tests?

Add a rule in your Intercept YAML policy under the tools section for find_flaky_tests. 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 find_flaky_tests?

find_flaky_tests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_flaky_tests?

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

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

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