24 tools from the Buildkite MCP Server, categorised by risk level.
View the Buildkite policy →access_token Get access token details and scopes 3/5 current_user Get the current authenticated user 2/5 get_artifact Get details of a specific artifact 2/5 get_build Get details of a specific build 2/5 get_build_test_engine_runs Get test engine runs for a build 2/5 get_cluster Get details of a specific cluster 2/5 get_cluster_queue Get details of a specific cluster queue 2/5 get_pipeline Get details of a specific pipeline 2/5 list_annotations List annotations for a build 2/5 list_artifacts_for_build List artifacts for a build 2/5 list_artifacts_for_job List artifacts for a job 2/5 list_builds List builds with optional filtering 2/5 list_cluster_queues List queues in a cluster 2/5 list_clusters List all clusters in an organisation 2/5 list_pipelines List pipelines in an organisation 2/5 read_logs Read build logs 2/5 search_logs Search build logs by content 2/5 tail_logs Tail the end of build logs 2/5 user_token_organization Get the organisation for the user token 2/5 wait_for_build Wait for a build to complete 2/5 The Buildkite MCP server exposes 24 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Buildkite server.
Buildkite tools are categorised as Read (20), Write (2), Execute (2). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept