jira_workflow_get_transitions_tool
AI agents call jira_workflow_get_transitions_tool 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 'get_transitions' operation retrieves available workflow transitions for a Jira issue without modifying any data. This is a read-only query operation with no side effects. Confidence is moderate (0.85) rather than high because the description is empty, but the function name strongly implies data retrieval rather than modification.
From the tool's definition Tool name contains 'get_transitions' which indicates retrieval of workflow transition information. The server context describes 'workflow transitions' as a read capability for issue management.
Attacks that exploit this kind of access
jira_workflow_get_transitions_tool. 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 jira_workflow_get_transitions_tool: 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.
jira_workflow_get_transitions_tool 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 jira_workflow_get_transitions_tool 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 jira_workflow_get_transitions_tool. 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.
jira_workflow_get_transitions_tool is provided by the Jira MCP Server MCP server (troylar/jira-mcp-server). 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 →