run_pipeline
Trigger a pipeline to run
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 invoke run_pipeline 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.
WHY ENFORCE A POLICY ON RUN_PIPELINE
run_pipeline 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.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
run_pipeline:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full CircleCI policy for all 15 tools.
DETAILS
MORE CIRCLECI TOOLS
run_rollback_pipeline Execute find_flaky_tests Read find_underused_resource_classes Read get_build_failure_logs Read get_job_test_results Read get_latest_pipeline_status Read list_component_versions Read list_followed_projects Read SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the run_pipeline tool do?
Trigger a pipeline to run. 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 run_pipeline?
Add a rule in your Intercept YAML policy under the tools section for run_pipeline. 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 run_pipeline?
run_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit run_pipeline?
Yes. Add a rate_limit block to the run_pipeline 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 run_pipeline completely?
Set action: deny in the Intercept policy for run_pipeline. 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_pipeline?
run_pipeline 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.