get_queue_issues
AI agents call get_queue_issues to retrieve information from MCP Atlassian + Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name strongly suggests data retrieval without side effects. No modification, deletion, or execution is implied. The 'get_' prefix and 'queue_issues' noun phrase are consistent with Read category operations. Confidence is moderate (0.70) rather than high (0.85+) due to the empty description, which prevents confirmation of exact behavior and parameters.
From the tool's definition Tool name 'get_queue_issues' indicates retrieval of issue queue data. The description is empty, but naming convention suggests a read operation typical of Jira queue/filter querying (similar pattern to sibling tools like 'get_agile_boards',…
Attacks that exploit this kind of access
get_queue_issues. It is categorised as a Read tool in the MCP Atlassian + Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian + Bitbucket MCP server in PolicyLayer and add a rule for get_queue_issues: 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 Atlassian + Bitbucket. Nothing to install.
get_queue_issues 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_queue_issues 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_queue_issues. 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_queue_issues is provided by the MCP Atlassian + Bitbucket MCP server (jellythomas/mcp-atlassian-with-bitbucket). 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 →