Get comprehensive details about a specific sprint including its name, start/end dates, goals, and all issues included in the sprint.
AI agents call get_sprint_details 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 sprint metadata and associated issue information without any side effects. It performs a query operation (get) that returns read-only data about sprint planning and status. No data is created, modified, deleted, or executed.
From the tool's definition Tool description states it 'Get[s] comprehensive details about a specific sprint' including 'name, start/end dates, goals, and all issues' — purely retrieval operations with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get comprehensive details about a specific sprint including its name, start/end dates, goals, and all issues included in the sprint. 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_sprint_details: 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_sprint_details 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_sprint_details 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_sprint_details. 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_sprint_details is provided by the Mcp Atlassian MCP server (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 →