bitbucket_list_repos
List Bitbucket repositories in a workspace.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bitbucket-list-repos.md
What bitbucket_list_repos does on UnClick
AI agents call bitbucket_list_repos to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Repos to return (max 100, default 25) |
username | string | Yes | Bitbucket username |
workspace | string | Yes | Workspace id |
app_password | string | Yes | Bitbucket app password |
Parameters from the server's own tool schema.
Why bitbucket_list_repos is rated Low
This tool retrieves and enumerates repository information from Bitbucket without any capability to modify, delete, or execute operations. It has a read-only purpose with minimal security impact even if misused by an AI agent, as it only exposes repository metadata already accessible to the authenticated user.
From the tool's definition Tool name includes 'list' which is a read-only query operation. Description states 'List Bitbucket repositories in a workspace' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs bitbucket_list_repos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_list_repos, this is the rule to start with:
bitbucket_list_repos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every bitbucket_list_repos call is checked against it from then on.
Questions about bitbucket_list_repos
List Bitbucket repositories in a workspace. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bitbucket_list_repos accepts 4 parameters: limit, username, workspace, app_password. Required: username, workspace, app_password. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for bitbucket_list_repos: 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 UnClick. Nothing to install.
bitbucket_list_repos 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 bitbucket_list_repos 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 bitbucket_list_repos. 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.
bitbucket_list_repos is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue