jira_transition_issue · Mcp Jira Stdio MCP: Risk & Policy

WHAT IT DOES

What jira_transition_issue does on Mcp Jira Stdio

AI agents use jira_transition_issue to create or update resources in Mcp Jira Stdio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Stdio environment.

WHY IT NEEDS A POLICY

Why jira_transition_issue needs a policy

This tool modifies issue state by transitioning it through workflow statuses and optionally setting resolution and adding comments. These are reversible state changes (issues can be transitioned back to previous states in most Jira workflows), making it Write rather than Destructive.

From the tool's definition Transitions a Jira issue to a new workflow status... Supports adding a comment and setting resolution during the transition.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_transition_issue Rate-limited

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

FAQ

Questions about jira_transition_issue

What does the jira_transition_issue tool do? +

Transitions a Jira issue to a new workflow status (e.g., "To Do" -> "In Progress" -> "Done"). Use jira_get_transitions first to discover available transitions. Supports adding a comment and setting resolution during the transition. It is categorised as a Write tool in the Mcp Jira Stdio 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_issue? +

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

What risk level is jira_transition_issue? +

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

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 Stdio MCP server (mcp-jira-stdio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.