Generate a sprint report for retrospectives. Returns issue counts and story points grouped by status categories, bug metrics, and label-specific tracking. Compares current sprint with previous sprint.
AI agents call jira_get_sprint_report 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 tool retrieves and aggregates existing JIRA data for reporting purposes without side effects. It compares and analyzes sprint information but does not create, modify, delete, or execute any operations. This is a pure read operation used for sprint retrospectives and analytics.
From the tool's definition Tool 'jira_get_sprint_report' generates and returns a report with aggregated metrics (issue counts, story points, bug metrics) grouped by status and labels, and compares sprints. The verb 'generate' and 'returns' indicate data retrieval and presentation only.
Attacks that exploit this kind of access
Generate a sprint report for retrospectives. Returns issue counts and story points grouped by status categories, bug metrics, and label-specific tracking. Compares current sprint with previous sprint. 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_report: 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_report 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_report 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_report. 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_report 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 →