Gets Bitbucket user profile details by username.
AI agents call bitbucket_get_user_profile to retrieve information from Mcp Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information from Bitbucket, which is a query operation with no side effects. It does not create, modify, delete, execute code, or affect financial systems. The blast radius of misuse is minimal—an attacker could only discover public or semi-public user profile metadata, which is typically already discoverable through the Bitbucket UI.
From the tool's definition Tool name 'bitbucket_get_user_profile' and description 'Gets Bitbucket user profile details by username' indicate data retrieval without modification. The verb 'Gets' and lack of any mutation language confirm this is a read-only operation.
Documented attack patterns abuse exactly the kind of access bitbucket_get_user_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Bitbucket, and nothing reaches the server without passing your rules. This is the rule we recommend for bitbucket_get_user_profile:
{
"version": "1",
"default": "deny",
"tools": {
"bitbucket_get_user_profile": {}
}
} bitbucket_get_user_profile 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.
Gets Bitbucket user profile details by username. It is categorised as a Read tool in the Mcp Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bitbucket MCP server in PolicyLayer and add a rule for bitbucket_get_user_profile: 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. Nothing to install.
bitbucket_get_user_profile 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_user_profile 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_user_profile. 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_user_profile is provided by the Mcp Bitbucket MCP server (n11techhub/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, 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.
18 Mcp Bitbucket tools catalogued and risk-classified — across an index of 43,000+ MCP servers.