AI agents use transitionIssue to create or update resources in MCP Atlassian Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Atlassian Server environment.
Transitioning an issue status modifies data within Jira but does not delete, destroy, or execute arbitrary code. The change is reversible (an issue can be transitioned back to a previous status). While it affects tracked work and could impact team coordination if misused by an AI agent, it falls into the Write category as a data modification action.
From the tool's definition Tool name 'transitionIssue' and description 'Transition the status of a Jira issue' indicate state modification of an existing Jira issue by changing its workflow status (e.g., To Do → In Progress → Done). This is a reversible change to issue metadata.
Documented attack patterns abuse exactly the kind of access transitionIssue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian Server, and nothing reaches the server without passing your rules. This is the rule we recommend for transitionIssue:
{
"version": "1",
"default": "deny",
"tools": {
"transitionIssue": {
"limits": [
{
"counter": "transitionissue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}transitionIssue 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 the status of a Jira issue. It is categorised as a Write tool in the MCP Atlassian Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Atlassian Server MCP server in PolicyLayer and add a rule for transitionIssue: 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 MCP Atlassian Server. Nothing to install.
transitionIssue 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 transitionIssue 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 transitionIssue. 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.
transitionIssue is provided by the MCP Atlassian Server MCP server (phuc-nt/mcp-atlassian-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 MCP Atlassian Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 MCP Atlassian Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.