AI agents use transition_issue to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
Transitioning an issue to a new status is a reversible modification of issue metadata. While it changes issue state, transitions are typically reversible in Jira (issues can be moved back to previous statuses via reverse transitions), distinguishing this from destructive operations.
From the tool's definition Tool name 'transition_issue' and description 'Transition a Jira issue to a new status' indicate the tool modifies issue state/status.
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": 30,
"scope": "grant"
}
]
}
}
}transition_issue 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 issue to a new status. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 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_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 (redhat-community-ai-tools/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 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.
30 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.