Transition an issue to a new status
AI agents invoke jira_transition_issue to trigger actions in Jira MCP 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.
This tool triggers a status/workflow transition in Jira, which is an external operation that changes the state of an issue (e.g., moving from 'In Progress' to 'Done'). It's not a simple data write/update of fields, but rather executing a workflow action. It has moderate blast radius since transitions can trigger automations, notifications, and workflow side effects, but is generally reversible by transitioning back.
From the tool's definition Transition an issue to a new status
Attacks that exploit this kind of access
Transition an issue to a new status. It is categorised as a Execute tool in the Jira MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jira MCP 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 Jira MCP Server. Nothing to install.
jira_transition_issue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 Jira MCP Server MCP server (sunwoobang/jira-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 →