transition_issue · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What transition_issue does on Jira MCP Server

AI agents use transition_issue 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 transition_issue needs a policy

This tool changes the workflow status of a Jira issue (e.g., from 'In Progress' to 'Done'). It modifies data but is generally reversible since issues can be transitioned back to previous states. It does not delete data or execute arbitrary code, placing it firmly in the Write category.

From the tool's definition Transition an issue to a different status

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transition_issue Rate-limited

transition_issue 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": {
    "transition_issue": {
      "limits": [
        {
          "counter": "transition_issue_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 transition_issue

What does the transition_issue tool do? +

Transition an issue to a different status. 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 transition_issue? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for transition_issue: 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 transition_issue? +

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

Can I rate-limit transition_issue? +

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

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

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