jira_transition · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_transition does on Jira MCP Server

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

This tool modifies the state/status of a Jira ticket, which is a reversible write operation. Status transitions can typically be undone by transitioning back. It does not delete data or execute code, placing it firmly in the Write category. Misuse could disrupt project workflows by moving tickets to incorrect states, hence medium severity.

From the tool's definition Change the status of a Jira ticket... transition by name... transitionId for direct transition

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_transition Rate-limited

jira_transition 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": {
    "jira_transition": {
      "limits": [
        {
          "counter": "jira_transition_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 jira_transition

What does the jira_transition tool do? +

Change the status of a Jira ticket. Use targetStatus to transition by name (auto-handles intermediate steps like In Progress), transitionId for direct transition, or omit both to list available transitions. 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 jira_transition? +

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

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

Can I rate-limit jira_transition? +

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

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

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