bb_get

// WHEN AI AGENTS USE THIS TOOL

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.

// WHY ENFORCE A POLICY ON BB_GET

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.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

atlassian-bitbucket.yaml

tools:
  bb_get:
    rules:
      - action: allow

See the full Atlassian Bitbucket policy for all 6 tools.

// DETAILS

Tool Name bb_get

Category Read

MCP Server Atlassian Bitbucket MCP Server

Risk Level Low

// MORE ATLASSIAN BITBUCKET TOOLS

Destructive bb_delete Write bb_clone Write bb_patch Write bb_post Write bb_put

// WHAT CAN GO WRONG

Agents calling read-class tools like bb_get have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the bb_get tool do? +

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.

How do I enforce a policy on bb_get? +

Add a rule in your Intercept YAML policy under the tools section for bb_get. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Atlassian Bitbucket MCP server.

What risk level is bb_get? +

bb_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bb_get? +

Yes. Add a rate_limit block to the bb_get 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 bb_get completely? +

Set action: deny in the Intercept 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.

What MCP server provides bb_get? +

bb_get is provided by the Atlassian Bitbucket MCP server (@aashari/mcp-server-atlassian-bitbucket). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Atlassian Bitbucket