Search for code across all repositories in a workspace.
AI agents call search_code 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 searches code without creating, modifying, deleting, or executing anything. It is a read-only operation that returns results. The low severity reflects minimal blast radius if misused—an AI agent searching code cannot damage systems or data, only potentially access sensitive source code it shouldn't see. Confidence is high because the description unambiguously describes search/retrieval.
From the tool's definition Tool name 'search_code' and description 'Search for code across all repositories in a workspace' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for code across all repositories in a workspace. 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 search_code: 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.
search_code 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 search_code 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 search_code. 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.
search_code 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 →