List all forks of a repository.
AI agents call list_repository_forks to retrieve information from Bitbucket Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing forks of a repository, which is a read-only operation. It queries data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could enumerate fork information but cannot alter state or compromise systems.
From the tool's definition Tool name 'list_repository_forks' and description 'List all forks of a repository' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List all forks of a repository. It is categorised as a Read tool in the Bitbucket Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for list_repository_forks: 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 Cloud MCP Server. Nothing to install.
list_repository_forks 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_repository_forks 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_repository_forks. 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_repository_forks is provided by the Bitbucket Cloud MCP Server MCP server (lexmata/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 →