jira_get_sprint_issues

Get all issues in a sprint

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/jira-get-sprint-issues.md

WHAT IT DOES

What jira_get_sprint_issues does on Sage MCP

AI agents call jira_get_sprint_issues to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why jira_get_sprint_issues is rated Low

This tool queries and returns sprint issues from Jira without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves existing data. The low severity reflects minimal blast radius — an AI agent misusing this would at worst retrieve unintended sprint information, but cannot corrupt or destroy data.

From the tool's definition Tool name contains 'get' and description states 'Get all issues in a sprint' — retrieves data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_get_sprint_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_get_sprint_issues, this is the rule to start with:

jira_get_sprint_issues Allowed

jira_get_sprint_issues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_get_sprint_issues": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every jira_get_sprint_issues call is checked against it from then on.

FAQ

Questions about jira_get_sprint_issues

What does the jira_get_sprint_issues tool do? +

Get all issues in a sprint. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_get_sprint_issues? +

Register the Sage 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 Sage MCP. Nothing to install.

What risk level is jira_get_sprint_issues? +

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

Can I rate-limit jira_get_sprint_issues? +

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.

How do I block jira_get_sprint_issues completely? +

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.

What MCP server provides jira_get_sprint_issues? +

jira_get_sprint_issues is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →