Get available transitions for a Jira issue.
AI agents call get_issue_transitions to retrieve information from Jira MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves metadata about possible workflow transitions for an issue—it does not execute transitions, modify the issue, or have side effects. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name is 'get_issue_transitions' and description states 'Get available transitions for a Jira issue.' This is a retrieval operation that queries available state transitions without modifying data.
Documented attack patterns abuse exactly the kind of access get_issue_transitions 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 get_issue_transitions:
{
"version": "1",
"default": "deny",
"tools": {
"get_issue_transitions": {}
}
}get_issue_transitions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get available transitions for a Jira issue. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for get_issue_transitions: 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.
get_issue_transitions 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 get_issue_transitions 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 get_issue_transitions. 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.
get_issue_transitions 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.