transitionJiraIssue · Atlassian Multi MCP: Risk & Policy

WHAT IT DOES

What transitionJiraIssue does on Atlassian Multi

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

WHY IT NEEDS A POLICY

Why transitionJiraIssue needs a policy

Transitioning a Jira issue changes its workflow state (e.g., from 'To Do' to 'In Progress' or 'Done'). This is a reversible modification to issue metadata — it can be transitioned back — so it qualifies as Write rather than Execute or Destructive. Misuse could disrupt project workflows or prematurely close issues, giving it medium severity.

From the tool's definition Transition a Jira issue to a new workflow status

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transitionJiraIssue Rate-limited

transitionJiraIssue 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": {
    "transitionJiraIssue": {
      "limits": [
        {
          "counter": "transitionjiraissue_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 Atlassian Multi, so you can run agents against it safely.

FAQ

Questions about transitionJiraIssue

What does the transitionJiraIssue tool do? +

Transition a Jira issue to a new workflow status. It is categorised as a Write tool in the Atlassian Multi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on transitionJiraIssue? +

Register the Atlassian Multi MCP server in PolicyLayer and add a rule for transitionJiraIssue: 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 Atlassian Multi. Nothing to install.

What risk level is transitionJiraIssue? +

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

Can I rate-limit transitionJiraIssue? +

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

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

transitionJiraIssue is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.