Read any Bitbucket data. Returns TOON format by default (30-60% fewer tokens than JSON). IMPORTANT - Cost Optimization: - ALWAYS use jq param to filter response fields. Unfiltered responses are very expensive! - Use pagelen query param to restrict result count (e.g., pagelen: "5") - If unsure abo...
Risk signalsAccepts file system path (path)
Part of the Atlassian Bitbucket server.
Free to start. No card required.
AI agents call bb_get to retrieve information from Atlassian Bitbucket 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.
Even though bb_get 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.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"bb_get": {}
}
}See the full Atlassian Bitbucket policy for all 6 tools.
These attack patterns abuse exactly the kind of access bb_get gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read any Bitbucket data. Returns TOON format by default (30-60% fewer tokens than JSON). IMPORTANT - Cost Optimization: - ALWAYS use jq param to filter response fields. Unfiltered responses are very expensive! - Use pagelen query param to restrict result count (e.g., pagelen: "5") - If unsure about available fields, first fetch ONE item with pagelen: "1" and NO jq filter to explore the schema, then use jq in subsequent calls Schema Discovery Pattern: 1. First call: path: "/workspaces", queryParams: {"pagelen": "1"} (no jq) - explore available fields 2. Then use: jq: "values[*].{slug: slug, name: name, uuid: uuid}" - extract only what you need Output format: TOON (default, token-efficient) or JSON (outputFormat: "json") Common paths: - /workspaces - list workspaces - /repositories/{workspace} - list repos in workspace - /repositories/{workspace}/{repo} - get repo details - /repositories/{workspace}/{repo}/pullrequests - list PRs - /repositories/{workspace}/{repo}/pullrequests/{id} - get PR details - /repositories/{workspace}/{repo}/pullrequests/{id}/comments - list PR comments - /repositories/{workspace}/{repo}/pullrequests/{id}/diff - get PR diff - /repositories/{workspace}/{repo}/refs/branches - list branches - /repositories/{workspace}/{repo}/commits - list commits - /repositories/{workspace}/{repo}/src/{commit}/{filepath} - get file content - /repositories/{workspace}/{repo}/diff/{source}..{destination} - compare branches/commits Query params: pagelen (page size), page (page number), q (filter), sort (order), fields (sparse response) Example filters (q param): state="OPEN", source.branch.name="feature", title~"bug" JQ examples: values[*].slug, values[0], values[*].{name: name, uuid: uuid} The /2.0 prefix is added automatically. API reference: https://developer.atlassian.com/cloud/bitbucket/rest/. It is categorised as a Read tool in the Atlassian Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Bitbucket MCP server in PolicyLayer and add a rule for bb_get: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Atlassian Bitbucket. Nothing to install.
bb_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bb_get rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for bb_get. 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.
bb_get is provided by the Atlassian Bitbucket MCP server (@aashari/mcp-server-atlassian-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Atlassian Bitbucket tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.