Get all issues in a specific sprint. Returns issue keys, summaries, statuses, and assignees by default. Use the fields parameter to customize which fields are returned.
AI agents call jira_get_sprint_issues to retrieve information from JIRA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query tool that retrieves sprint data without side effects. It allows customization of returned fields but only for read purposes. No destructive, financial, or code-execution capabilities are present. The blast radius of misuse is minimal — exposure of potentially sensitive sprint planning information, but no data can be modified or deleted.
From the tool's definition Tool description explicitly states 'Get all issues in a specific sprint' and 'Returns issue keys, summaries, statuses, and assignees' — pure data retrieval with customizable output fields. No modification, deletion, or execution of code mentioned.
Attacks that exploit this kind of access
Get all issues in a specific sprint. Returns issue keys, summaries, statuses, and assignees by default. Use the fields parameter to customize which fields are returned. It is categorised as a Read tool in the JIRA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for jira_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 JIRA MCP Server. Nothing to install.
jira_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 jira_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 jira_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.
jira_get_sprint_issues is provided by the JIRA MCP Server MCP server (suppleaardvark/jira-mcp-server). 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 →