List all sprints with optional project and status filters. e.g., project:
AI agents call list_sprints to retrieve information from Issue Tracker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns sprint information based on optional filters. It has no side effects—it does not create, modify, delete, or execute operations. It is a straightforward read operation that retrieves existing data from the issue tracker. The minimal blast radius of misuse (returning sprint data) and lack of any reversible or irreversible mutations justifies the 'low' severity classification.
From the tool's definition Tool name 'list_sprints' and description 'List all sprints with optional project and status filters' indicate a retrieval operation with no data modification or destructive capability.
Attacks that exploit this kind of access
List all sprints with optional project and status filters. e.g., project:. It is categorised as a Read tool in the Issue Tracker MCP MCP Server, which means it retrieves data without modifying state.
Register the Issue Tracker MCP server in PolicyLayer and add a rule for list_sprints: 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 Issue Tracker MCP. Nothing to install.
list_sprints 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 list_sprints 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 list_sprints. 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.
list_sprints is provided by the Issue Tracker MCP server (josephtandle/jira-mcp-mcp). 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 →