List default reviewers for a project.
AI agents call list_default_reviewers to retrieve information from Bitbucket MCP Server 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 information about default reviewers assigned to a project. It performs a read-only operation that has no side effects—it neither creates, modifies, deletes, executes code, nor commits financial transactions. The blast radius of misuse is minimal, as an attacker gains only visibility into reviewer assignments, which is typically non-sensitive metadata in most organizations.
From the tool's definition Tool name is 'list_default_reviewers' and description states 'List default reviewers for a project.' The verb 'list' indicates a retrieval operation with no modification of data.
Attacks that exploit this kind of access
List default reviewers for a project. It is categorised as a Read tool in the Bitbucket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP Server MCP server in PolicyLayer and add a rule for list_default_reviewers: 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 MCP Server. Nothing to install.
list_default_reviewers 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 list_default_reviewers 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 list_default_reviewers. 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.
list_default_reviewers is provided by the Bitbucket MCP Server MCP server (korfu/mcp-bitbucket). 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 →