get_my_current_sprint_issues

Get all issues assigned to you in the currently active sprint(s). Useful for daily standups or checking your current sprint workload. Can filter by specific board or project.

Server Mcp Atlassian mcp-atlassian
Category Read
Risk class Low
Parameters 00 required

What get_my_current_sprint_issues does on Mcp Atlassian

AI agents call get_my_current_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.

Why get_my_current_sprint_issues needs a policy

This tool retrieves and queries sprint issue data belonging to the authenticated user. It performs no side effects, creates no data, executes no code, and causes no irreversible changes. The filtering capability ('Can filter by specific board or project') is a read-only query parameter. Classification as Read is appropriate.

From the tool's definition Tool description states 'Get all issues assigned to you in the currently active sprint(s)' and describes use for 'daily standups or checking your current sprint workload'—pure retrieval operations with no modification, deletion, or execution.

Questions about get_my_current_sprint_issues

What does the get_my_current_sprint_issues tool do? +

Get all issues assigned to you in the currently active sprint(s). Useful for daily standups or checking your current sprint workload. Can filter by specific board or project. It is categorised as a Read tool in the Mcp Atlassian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_my_current_sprint_issues? +

Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for get_my_current_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.

What risk level is get_my_current_sprint_issues? +

get_my_current_sprint_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_my_current_sprint_issues? +

Yes. Add a rate_limit block to the get_my_current_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.

How do I block get_my_current_sprint_issues completely? +

Set action: deny in the PolicyLayer policy for get_my_current_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.

What MCP server provides get_my_current_sprint_issues? +

get_my_current_sprint_issues 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.