update_status · Jira MCP: Risk & Policy

WHAT IT DOES

What update_status does on Jira

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

WHY IT NEEDS A POLICY

Why update_status needs a policy

The tool modifies existing Jira ticket data (status field) but does not delete or destroy information. Status updates in Jira are typically reversible workflow transitions. While this could impact ticket management workflows, it lacks the irreversibility of Destructive actions or the immediate execution risks of Execute category tools. Classified as Write due to its data modification nature with reversible effects.

From the tool's definition Tool name 'update_status' and description 'Update the status of a Jira ticket' indicate modification of ticket state. This is reversible—status changes can be undone by updating to a previous status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_status Rate-limited

update_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": {
    "update_status": {
      "limits": [
        {
          "counter": "update_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 Jira, so you can run agents against it safely.

FAQ

Questions about update_status

What does the update_status tool do? +

Update the status of a Jira ticket. It is categorised as a Write tool in the Jira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_status? +

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

What risk level is update_status? +

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

Can I rate-limit update_status? +

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

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

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