Get available workflow transitions for a Jira issue
AI agents call getTransitionsForJiraIssue to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available workflow transitions for an issue—it queries the current state and possible next states without creating, modifying, deleting, or executing any changes. It is purely informational and has no side effects on the system or data. This is a standard Read category tool with low severity since it only exposes workflow metadata.
From the tool's definition Tool name 'getTransitionsForJiraIssue' and description 'Get available workflow transitions for a Jira issue' indicate a read-only query operation that retrieves metadata about possible state changes without making any modifications.
Attacks that exploit this kind of access
Get available workflow transitions for a Jira issue. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for getTransitionsForJiraIssue: 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 Atlassian Multi. Nothing to install.
getTransitionsForJiraIssue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getTransitionsForJiraIssue 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 getTransitionsForJiraIssue. 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.
getTransitionsForJiraIssue is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-mcp). 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 →