This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bitbucket-get-repo.md
What bitbucket_get_repo does on UnClick
AI agents call bitbucket_get_repo 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 |
|---|---|---|---|
repo | string | Yes | Repository slug |
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_get_repo is rated Low
This tool retrieves information about a Bitbucket repository. The verb 'get' combined with the read-only nature of fetching repository details (likely metadata, configuration, or summary info) classifies it as a Read operation. There is no indication of code execution, data modification, deletion, or financial transactions.
From the tool's definition Tool name 'bitbucket_get_repo' and description 'Get a single Bitbucket repository' indicate retrieval of repository metadata with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs bitbucket_get_repo 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_get_repo, this is the rule to start with:
bitbucket_get_repo 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_get_repo call is checked against it from then on.
Questions about bitbucket_get_repo
Get a single Bitbucket repository. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bitbucket_get_repo accepts 4 parameters: repo, username, workspace, app_password. Required: repo, 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_get_repo: 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_get_repo 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_get_repo 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_get_repo. 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_get_repo 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