change_status · AI-Powered Jira MCP Server MCP

WHAT IT DOES

What change_status does on AI-Powered Jira MCP Server

AI agents use change_status to create or update resources in AI-Powered Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI-Powered Jira MCP Server environment.

WHY IT NEEDS A POLICY

Why change_status needs a policy

This tool modifies the workflow state of a Jira issue, which is a reversible write operation. Status changes can be undone by transitioning back to a prior state, so it does not qualify as Destructive. Misuse could disrupt project workflows (e.g., prematurely closing or reopening tickets), warranting a medium severity rating.

From the tool's definition Change the status/workflow state of a Jira issue

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_status Rate-limited

change_status 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": {
    "change_status": {
      "limits": [
        {
          "counter": "change_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about change_status

What does the change_status tool do? +

Change the status/workflow state of a Jira issue. It is categorised as a Write tool in the AI-Powered Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on change_status? +

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

What risk level is change_status? +

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

Can I rate-limit change_status? +

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

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

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