List all repositories in a Bitbucket Server project
AI agents call list_repositories to retrieve information from Mcp Bitbucket 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 returns repository metadata without modifying, creating, or deleting any data. It is a simple enumeration/listing operation typical of Read category tools. The low severity reflects that repository names and existence are typically non-sensitive information in most organizational contexts, though confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'list_repositories' and description 'List all repositories in a Bitbucket Server project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all repositories in a Bitbucket Server project. It is categorised as a Read tool in the Mcp Bitbucket Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bitbucket Server MCP server in PolicyLayer and add a rule for list_repositories: 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 Mcp Bitbucket Server. Nothing to install.
list_repositories 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_repositories 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_repositories. 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_repositories is provided by the Mcp Bitbucket Server MCP server (mcp-bitbucket-server). 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 →