add_to_sprint · Issue Tracker MCP: Risk & Policy

WHAT IT DOES

What add_to_sprint does on Issue Tracker MCP

AI agents use add_to_sprint to create or update resources in Issue Tracker MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Issue Tracker MCP environment.

WHY IT NEEDS A POLICY

Why add_to_sprint needs a policy

This tool creates or modifies sprint data (issue-to-sprint associations) without deleting or permanently destroying information. The action is reversible—issues can be removed from sprints. While it affects workflow state, the impact is limited to sprint planning operations on a single project management system.

From the tool's definition Tool description: 'Add one or more issues to a sprint' — this modifies sprint composition by adding issues, a reversible state change to a project management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_to_sprint Rate-limited

add_to_sprint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_to_sprint": {
      "limits": [
        {
          "counter": "add_to_sprint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Issue Tracker MCP, so you can run agents against it safely.

FAQ

Questions about add_to_sprint

What does the add_to_sprint tool do? +

Add one or more issues to a sprint. e.g., sprintId:. It is categorised as a Write tool in the Issue Tracker MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_sprint? +

Register the Issue Tracker MCP server in PolicyLayer and add a rule for add_to_sprint: 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.

What risk level is add_to_sprint? +

add_to_sprint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_sprint? +

Yes. Add a rate_limit block to the add_to_sprint 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 add_to_sprint completely? +

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

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