jira_get_transitions

Get available transitions for a Jira issue

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/jira-get-transitions.md

WHAT IT DOES

What jira_get_transitions does on ScopeGate

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

RISK

Why jira_get_transitions is rated Low

This tool retrieves metadata about available state transitions for a Jira issue. It performs a read-only query with no side effects—it does not create, modify, delete, or execute any changes. The blast radius of misuse is minimal, as an attacker could only enumerate workflow states, not alter issues or data.

From the tool's definition Tool name 'jira_get_transitions' and description 'Get available transitions for a Jira issue' indicate a retrieval operation that queries the state of a Jira issue without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_get_transitions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, 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:

jira_get_transitions Allowed

jira_get_transitions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every jira_get_transitions call is checked against it from then on.

FAQ

Questions about jira_get_transitions

What does the jira_get_transitions tool do? +

Get available transitions for a Jira issue. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_get_transitions? +

Register the ScopeGate 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 ScopeGate. Nothing to install.

What risk level is jira_get_transitions? +

jira_get_transitions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit jira_get_transitions? +

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.

How do I block jira_get_transitions completely? +

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.

What MCP server provides jira_get_transitions? +

jira_get_transitions is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →