jira_get_transitions

What jira_get_transitions does on Sage MCP

AI agents call jira_get_transitions to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why jira_get_transitions is rated Low

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.

The rule that runs jira_get_transitions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_get_transitions, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_get_transitions": {}
  }
}

Questions about jira_get_transitions