Get details of a specific issue.
AI agents call get_issue to retrieve information from Bitbucket Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves issue metadata and details from Bitbucket Cloud without modifying, deleting, or executing anything. It is purely informational (Read category). Severity is low because the blast radius of an AI agent retrieving issue details is minimal; issues are typically non-sensitive or already accessible to authenticated users.
From the tool's definition Tool name is 'get_issue' and description states it 'Get details of a specific issue' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a specific issue. It is categorised as a Read tool in the Bitbucket Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for get_issue: 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 Cloud MCP Server. Nothing to install.
get_issue 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_issue 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_issue. 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_issue is provided by the Bitbucket Cloud MCP Server MCP server (lexmata/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 →