get_service_desk_queues
AI agents call get_service_desk_queues to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a retrieval operation. Service Desk queues are typically configuration or status data that a read operation would fetch. No creation, modification, deletion, execution, or financial impact is implied.
From the tool's definition Tool name 'get_service_desk_queues' indicates retrieval of queue information. The empty description limits evidence, but the 'get_' prefix and context among sibling tools like 'get_agile_boards', 'get_all_projects', and 'get_comments' all pattern-match to…
Attacks that exploit this kind of access
get_service_desk_queues. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for get_service_desk_queues: 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. Nothing to install.
get_service_desk_queues 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_service_desk_queues 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_service_desk_queues. 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_service_desk_queues is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.