Transition an issue through workflow (e.g., move to
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.
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.
Documented attack patterns abuse exactly the kind of access jira_transition_issue 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_transition_issue:
{
"version": "1",
"default": "deny",
"tools": {
"jira_transition_issue": {
"limits": [
{
"counter": "jira_transition_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
jira_transition_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
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.