jira_transition_issue

Transition an issue through workflow (e.g., move to

SERVERSage MCP SOURCEsagemcp/sagemcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/jira-transition-issue.md

WHAT IT DOES

What jira_transition_issue does on Sage MCP

AI agents use jira_transition_issue to create or update resources in Sage MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.

RISK

Why jira_transition_issue is rated Medium

Transitioning an issue changes its workflow state (e.g., Open→In Progress→Done), which modifies data reversibly. This is a Write operation since the state change can be undone by transitioning back to a previous state. Severity is medium because unintended transitions could disrupt project tracking and team workflows, but the effect is not destructive and has no financial impact.

From the tool's definition Tool name 'jira_transition_issue' and description 'Transition an issue through workflow (e.g., move to...' indicate modifying issue status/state in Jira.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_transition_issue 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_transition_issue, this is the rule to start with:

jira_transition_issue Rate-limited

jira_transition_issue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_transition_issue": {
      "limits": [
        {
          "counter": "jira_transition_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about jira_transition_issue

What does the jira_transition_issue tool do? +

Transition an issue through workflow (e.g., move to. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jira_transition_issue? +

Register the Sage MCP server in PolicyLayer and add a rule for jira_transition_issue: 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.

What risk level is jira_transition_issue? +

jira_transition_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_transition_issue? +

Yes. Add a rate_limit block to the jira_transition_issue 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_transition_issue completely? +

Set action: deny in the PolicyLayer policy for jira_transition_issue. 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_transition_issue? +

jira_transition_issue 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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →