move_issue_to_sprint · Raalarcon Jira MCP: Risk & Policy

WHAT IT DOES

What move_issue_to_sprint does on Raalarcon Jira

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

WHY IT NEEDS A POLICY

Why move_issue_to_sprint needs a policy

Moving an issue between sprints modifies project state but is easily reversible (issues can be moved again or removed from sprints). This is a standard Write operation in agile project management. Severity is medium because misuse could disrupt sprint planning, but the change is non-destructive and the blast radius is limited to workflow disruption rather than data loss.

From the tool's definition Tool description states 'Move an issue to a specific sprint' and 'add tickets to the current sprint' — these are reversible modifications to issue state/sprint membership, not deletions or financial transactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_issue_to_sprint Rate-limited

move_issue_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": {
    "move_issue_to_sprint": {
      "limits": [
        {
          "counter": "move_issue_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 Raalarcon Jira, so you can run agents against it safely.

FAQ

Questions about move_issue_to_sprint

What does the move_issue_to_sprint tool do? +

Move an issue to a specific sprint. This is the main function to add tickets to the current sprint. It is categorised as a Write tool in the Raalarcon Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_issue_to_sprint? +

Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for move_issue_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 Raalarcon Jira. Nothing to install.

What risk level is move_issue_to_sprint? +

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

Can I rate-limit move_issue_to_sprint? +

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

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

move_issue_to_sprint is provided by the Raalarcon Jira MCP server (raalarcon-jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.