get_sprint_issues
AI agents call get_sprint_issues 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 issues from a Jira agile board, a query operation with no side effects. It fits the Read category definition of retrieving or querying data. Severity is low because reading existing issue data poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name 'get_sprint_issues' indicates a retrieval operation with no mutation implied. Sibling tools include read-only operations like 'get_agile_boards', 'get_all_projects', 'get_comments', and 'download_*' functions, suggesting this server's tools are…
Attacks that exploit this kind of access
get_sprint_issues. 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_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. Nothing to install.
get_sprint_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_sprint_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_sprint_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_sprint_issues 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.