AI agents call jira_get_transitions to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists available workflow transitions (possible next states) for a given issue. It queries existing data without creating, modifying, deleting, or executing any transitions. The word 'Get' and the read-only nature of listing available options classify this as a Read operation. The blast radius is minimal since it only exposes metadata about what could be done, not what will be done.
From the tool's definition Tool name 'jira_get_transitions' and description 'Get available workflow transitions for an issue' indicate a query operation that retrieves metadata about possible state changes for a Jira issue, with no modification or execution of those transitions.
Documented attack patterns abuse exactly the kind of access jira_get_transitions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_get_transitions:
{
"version": "1",
"default": "deny",
"tools": {
"jira_get_transitions": {}
}
}jira_get_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 workflow transitions for an issue. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for jira_get_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 Sage MCP. Nothing to install.
jira_get_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 jira_get_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 jira_get_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.
jira_get_transitions is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.