get_build_failure_logs
Retrieve detailed failure logs from builds
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 get_build_failure_logs 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 GET_BUILD_FAILURE_LOGS
Even though get_build_failure_logs 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.
tools:
get_build_failure_logs:
rules:
- action: allowSee the full CircleCI policy for all 15 tools.
DETAILS
MORE CIRCLECI TOOLS
find_flaky_tests Read find_underused_resource_classes Read get_job_test_results Read get_latest_pipeline_status Read list_component_versions Read list_followed_projects Read create_prompt_template Write run_pipeline Execute SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the get_build_failure_logs tool do?
Retrieve detailed failure logs from builds. 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 get_build_failure_logs?
Add a rule in your Intercept YAML policy under the tools section for get_build_failure_logs. 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 get_build_failure_logs?
get_build_failure_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit get_build_failure_logs?
Yes. Add a rate_limit block to the get_build_failure_logs 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 get_build_failure_logs completely?
Set action: deny in the Intercept policy for get_build_failure_logs. 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 get_build_failure_logs?
get_build_failure_logs 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.