Search repositories in Bitbucket using Bitbucket
AI agents call bb_search_repositories to retrieve information from MCP Bitbucket Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about repositories through a search query. It is a read-only operation that does not create, modify, delete, or execute anything. No AI agent misuse of a search function would cause irreversible damage or harmful side effects. Severity is low because the blast radius is minimal—search results contain only existing metadata that the authenticated user is authorized to access.
From the tool's definition Tool name 'bb_search_repositories' and description 'Search repositories in Bitbucket' indicate a query/retrieval operation with no side effects. Search operations retrieve data without modifying, deleting, or executing code.
Documented attack patterns abuse exactly the kind of access bb_search_repositories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Bitbucket Python, and nothing reaches the server without passing your rules. This is the rule we recommend for bb_search_repositories:
{
"version": "1",
"default": "deny",
"tools": {
"bb_search_repositories": {}
}
} bb_search_repositories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search repositories in Bitbucket using Bitbucket. It is categorised as a Read tool in the MCP Bitbucket Python MCP Server, which means it retrieves data without modifying state.
Register the MCP Bitbucket Python MCP server in PolicyLayer and add a rule for bb_search_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 Python. Nothing to install.
bb_search_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 bb_search_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 bb_search_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.
bb_search_repositories is provided by the MCP Bitbucket Python MCP server (kallows/mcp-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Bitbucket Python, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Bitbucket Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.