Transition a JIRA ticket to a different status
AI agents use transition-ticket to create or update resources in JIRA MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JIRA MCP environment.
This falls under Write rather than Execute because it modifies data (ticket status) reversibly through a standard JIRA workflow operation. It is not Destructive because status transitions are not permanent deletions and can be undone by transitioning again. It is not Execute because it does not run arbitrary code or scripts—it invokes a predefined JIRA workflow action.
From the tool's definition The tool 'transition-ticket' modifies ticket state by changing its status to a different workflow state. This is a state change operation that is reversible (tickets can transition back or to other states).
Documented attack patterns abuse exactly the kind of access transition-ticket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for transition-ticket:
{
"version": "1",
"default": "deny",
"tools": {
"transition-ticket": {
"limits": [
{
"counter": "transition-ticket_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}transition-ticket 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.
Free to start. No card required.
Transition a JIRA ticket to a different status. It is categorised as a Write tool in the JIRA MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JIRA MCP server in PolicyLayer and add a rule for transition-ticket: 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. Nothing to install.
transition-ticket 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 transition-ticket 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-ticket. 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-ticket is provided by the JIRA MCP server (mankowskinick/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JIRA MCP, 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.
14 JIRA MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.