jira_transition_issue · MCP JIRA Server MCP: Risk & Policy

WHAT IT DOES

What jira_transition_issue does on MCP JIRA Server

AI agents invoke jira_transition_issue to trigger actions in MCP JIRA Server. 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 jira_transition_issue needs a policy

Transitioning a JIRA issue triggers a workflow state change (e.g., 'In Progress' to 'Done'), which is an external operation that modifies issue state. This is an Execute action as it triggers workflow operations. The description is empty, lowering confidence slightly, but the name and server context make the purpose clear. It's not purely Write (data creation/modification) but rather execution of a workflow action.

From the tool's definition Tool name 'jira_transition_issue' and server description mentions 'workflow transitions' as a supported capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_transition_issue Rate-limited

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

FAQ

Questions about jira_transition_issue

What does the jira_transition_issue tool do? +

jira_transition_issue. It is categorised as a Execute tool in the MCP JIRA Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jira_transition_issue? +

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

What risk level is jira_transition_issue? +

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

Can I rate-limit jira_transition_issue? +

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

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

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