jira_workflow_transition_tool · Jira MCP Server MCP

WHAT IT DOES

What jira_workflow_transition_tool does on Jira MCP Server

AI agents invoke jira_workflow_transition_tool to trigger actions in Jira MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why jira_workflow_transition_tool needs a policy

Workflow transitions in Jira move issues between states (e.g., Open → In Progress → Closed), which are external operations that trigger side effects such as notifications, automation rules, and status changes. This maps to Execute. The empty description lowers confidence.

From the tool's definition Tool name 'jira_workflow_transition_tool' suggests triggering workflow state transitions in Jira; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_workflow_transition_tool Rate-limited

jira_workflow_transition_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_workflow_transition_tool": {
      "limits": [
        {
          "counter": "jira_workflow_transition_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_workflow_transition_tool

What does the jira_workflow_transition_tool tool do? +

jira_workflow_transition_tool. It is categorised as a Execute tool in the Jira MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jira_workflow_transition_tool? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for jira_workflow_transition_tool: 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 Jira MCP Server. Nothing to install.

What risk level is jira_workflow_transition_tool? +

jira_workflow_transition_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jira_workflow_transition_tool? +

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

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

jira_workflow_transition_tool is provided by the Jira MCP Server MCP server (troylar/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.