current_user
Get the current authenticated user
Part of the Buildkite MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call current_user to retrieve information from Buildkite 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 CURRENT_USER
Even though current_user 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:
current_user:
rules:
- action: allowSee the full Buildkite policy for all 22 tools.
DETAILS
MORE BUILDKITE TOOLS
list_pipelines Read get_pipeline Read list_builds Read get_build Read get_build_test_engine_runs Read list_clusters Read get_cluster Read list_cluster_queues Read 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 current_user tool do?
Get the current authenticated user. It is categorised as a Read tool in the Buildkite MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on current_user?
Add a rule in your Intercept YAML policy under the tools section for current_user. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Buildkite MCP server.
What risk level is current_user?
current_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit current_user?
Yes. Add a rate_limit block to the current_user 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 current_user completely?
Set action: deny in the Intercept policy for current_user. 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 current_user?
current_user is provided by the Buildkite MCP server (buildkite/buildkite-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON BUILDKITE
Open source. One binary. Zero dependencies.