update_ticket_fields · Jira MCP: Risk & Policy

WHAT IT DOES

What update_ticket_fields does on Jira

AI agents use update_ticket_fields 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_ticket_fields needs a policy

This tool modifies ticket metadata reversibly (fields can be updated again to different values or previous states). While it affects project tracking and team coordination, it does not delete data (Destructive), execute code (Execute), create financial obligations (Financial), or merely read data (Read). Write category applies because it creates or modifies data reversibly.

From the tool's definition Tool updates Jira ticket fields including 'original estimate, story points, labels, assignee, priority, due date, etc.' These are reversible modifications to existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_ticket_fields Rate-limited

update_ticket_fields 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_ticket_fields": {
      "limits": [
        {
          "counter": "update_ticket_fields_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_ticket_fields

What does the update_ticket_fields tool do? +

Update fields of a Jira ticket (e.g., original estimate, story points, labels, assignee, priority, due date, etc.). 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_ticket_fields? +

Register the Jira MCP server in PolicyLayer and add a rule for update_ticket_fields: 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_ticket_fields? +

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

Can I rate-limit update_ticket_fields? +

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

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

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