AI agents call get_code_review_checklist to retrieve information from Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data (a code review checklist) without modifying, deleting, or executing any operations. It is purely informational and serves as a lookup for review guidelines. The low severity reflects that misuse would only expose internal review standards, not enable data destruction, financial impact, or arbitrary code execution.
From the tool's definition Tool description states 'Get code review checklist' — a retrieval operation with no modification or side effects. It fetches repository-specific guidelines for review purposes.
Attacks that exploit this kind of access
Get code review checklist which acts as a guideline to review pull request. LLM must call this to get repository specific review guidelines. It is categorised as a Read tool in the Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP server in PolicyLayer and add a rule for get_code_review_checklist: 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 Bitbucket. Nothing to install.
get_code_review_checklist 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 get_code_review_checklist 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 get_code_review_checklist. 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.
get_code_review_checklist is provided by the Bitbucket MCP server (jishadmt/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →