AI agents call get_bitbucket_creds to retrieve information from Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored credentials without modifying, deleting, or executing any operations. It falls under the Read category as it queries and returns data. Severity is high because exposure of Bitbucket credentials could enable unauthorized repository access, code manipulation, or other account takeovers, making misuse by an untrusted agent highly damaging despite the read-only nature of the operation itself.
From the tool's definition Tool name 'get_bitbucket_creds' and description 'Retrieve Bitbucket credentials from environment variables' indicate data retrieval with no modification. However, the data retrieved (credentials) is highly sensitive.
Attacks that exploit this kind of access
Retrieve Bitbucket credentials from environment variables. It is categorised as a Read tool in the Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP server in PolicyLayer and add a rule for get_bitbucket_creds: 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. Nothing to install.
get_bitbucket_creds 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 get_bitbucket_creds 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 get_bitbucket_creds. 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.
get_bitbucket_creds is provided by the Bitbucket MCP server (jishadmt/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 →