transition_issue · Raalarcon Jira MCP: Risk & Policy

WHAT IT DOES

What transition_issue does on Raalarcon Jira

AI agents invoke transition_issue to trigger actions in Raalarcon Jira. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why transition_issue needs a policy

Transitioning an issue changes its workflow state in Jira (e.g., Open → In Progress → Done). This triggers external state changes and workflow actions in Jira, which qualifies as Execute. It modifies state but is generally reversible (you can transition back), so it doesn't reach Destructive. Misuse could disrupt sprint workflows or prematurely close issues, giving it medium severity.

From the tool's definition Move a Jira issue to a different status/state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transition_issue Rate-limited

transition_issue stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 transition_issue

What does the transition_issue tool do? +

Move a Jira issue to a different status/state. It is categorised as a Execute tool in the Raalarcon Jira MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transition_issue? +

Register the Raalarcon Jira 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 Raalarcon Jira. Nothing to install.

What risk level is transition_issue? +

transition_issue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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