AI agents use jira_transition_issue to create or update resources in Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian environment.
Transitioning an issue changes its workflow status (e.g., from 'In Progress' to 'Done'), which is a reversible state modification. It does not delete data, execute code, or involve financial operations. It can be undone by transitioning back, making it a Write operation. Misuse could disrupt workflows or prematurely close issues, hence medium severity.
From the tool's definition Transitions a Jira issue to a new status using a transition ID
Attacks that exploit this kind of access
Transitions a Jira issue to a new status using a transition ID. It is categorised as a Write tool in the Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian 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 Atlassian. Nothing to install.
jira_transition_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
jira_transition_issue is provided by the Atlassian MCP server (tingyiy/atlassian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →