reorder_jira_issues · JIRA MCP Server MCP: Risk & Policy

WHAT IT DOES

What reorder_jira_issues does on JIRA MCP Server

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

WHY IT NEEDS A POLICY

Why reorder_jira_issues needs a policy

Reordering issues modifies JIRA project state by changing the sequence or priority ranking of issues, which is a reversible write operation. While this does not create new issues or delete data, it alters existing metadata. The blast radius is medium: incorrect reordering could disrupt project planning workflows, but the change can be easily reversed.

From the tool's definition Tool name 'reorder_jira_issues' indicates modification of issue ordering/ranking state within JIRA. The sibling tool 'rank_jira_issues' confirms this server handles issue reordering as a write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reorder_jira_issues Rate-limited

reorder_jira_issues 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": {
    "reorder_jira_issues": {
      "limits": [
        {
          "counter": "reorder_jira_issues_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 JIRA MCP Server, so you can run agents against it safely.

FAQ

Questions about reorder_jira_issues

What does the reorder_jira_issues tool do? +

reorder_jira_issues. It is categorised as a Write tool in the JIRA MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reorder_jira_issues? +

Register the JIRA MCP Server MCP server in PolicyLayer and add a rule for reorder_jira_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 JIRA MCP Server. Nothing to install.

What risk level is reorder_jira_issues? +

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

Can I rate-limit reorder_jira_issues? +

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

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

reorder_jira_issues is provided by the JIRA MCP Server MCP server (rajsodhi-2/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.