AI agents invoke 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.
Transitioning an issue through workflow states triggers state changes in an external system (Jira). This is an operation that changes the status/state of a resource and may trigger automations, notifications, or other workflow actions. It's not purely a write (data creation/modification), but an execution of a workflow transition.
From the tool's definition Move an issue through workflow states
Documented attack patterns abuse exactly the kind of access transition_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transition_issue:
{
"version": "1",
"default": "deny",
"tools": {
"transition_issue": {
"limits": [
{
"counter": "transition_issue_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}transition_issue stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Move an issue through workflow states. 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 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.
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 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 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.
transition_issue is provided by the Jira MCP Server MCP server (sthirugn/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.