Get issues assigned to the current user in a specific sprint. Filters by assignee = currentUser(). Returns issue keys, summaries, statuses, and priorities sorted by status then priority by default. Use the fields parameter to customize which fields are returned.
AI agents call jira_get_my_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 tool retrieves and queries existing JIRA data filtered by the current user's assignments. It performs no creation, modification, deletion, or execution of external operations. The ability to customize returned fields via the 'fields' parameter does not change the fundamental read-only nature of the operation.
From the tool's definition Tool description states 'Get issues assigned to the current user in a specific sprint' and 'Returns issue keys, summaries, statuses, and priorities'. The verb 'Get' and 'Returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get issues assigned to the current user in a specific sprint. Filters by assignee = currentUser(). Returns issue keys, summaries, statuses, and priorities sorted by status then priority 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_my_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_my_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_my_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_my_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_my_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 →