Get sprints by name for a board, optionally filtered by state.
AI agents call get_sprints_by_name 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 sprint information from a Jira board filtered by name and optionally by state. It performs no modifications, deletions, or external operations—purely data retrieval. This is a low-risk read operation with no side effects. The blast radius is minimal as it only exposes existing sprint metadata that would typically be accessible to authorized Jira users.
From the tool's definition Tool name 'get_sprints_by_name' and description 'Get sprints by name for a board, optionally filtered by state' indicate retrieval of sprint data without modification or deletion. This is a query/fetch operation.
Documented attack patterns abuse exactly the kind of access get_sprints_by_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_sprints_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_sprints_by_name": {}
}
}get_sprints_by_name is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get sprints by name for a board, optionally filtered by state. 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 get_sprints_by_name: 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.
get_sprints_by_name 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 get_sprints_by_name 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 get_sprints_by_name. 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.
get_sprints_by_name is provided by the Jira MCP Server MCP server (redhat-community-ai-tools/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.