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.
This tool retrieves service desk queue information from Jira Service Desk, returning existing data without modification, deletion, or execution of external code. The 'get' prefix consistently indicates a Read operation across this MCP server. Although the description is empty, the naming convention and context from sibling tools strongly suggest a simple data retrieval function with minimal risk.
From the tool's definition Tool name 'get_service_desk_queues' uses the 'get' verb, which is a standard pattern for retrieval operations. The sibling tools include 'get_activities', 'get_agile_boards', 'get_all_projects', 'get_attachments' - all clearly Read operations.
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 (voarsh2/mcp-atlassian). 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 →