get_service_desk_for_project
AI agents call get_service_desk_for_project 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 is a standard read operation pattern. Even without explicit description, the sibling tools are all retrieval operations with no side effects. Service Desk configuration data retrieval represents minimal risk—it gathers information about an existing project's service desk setup without modifying, executing, or deleting anything.
From the tool's definition Tool name 'get_service_desk_for_project' with 'get' prefix indicates data retrieval. No description provided, but naming convention and context among sibling read-only tools (get_agile_boards, get_all_projects, get_comments, get_attachments) suggests querying…
Attacks that exploit this kind of access
get_service_desk_for_project. 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_for_project: 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_for_project 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_for_project 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_for_project. 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_for_project is provided by the MCP Atlassian MCP server (lklkxcxc/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 →