Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown). Only specified fields will be updated.
AI agents use jira_update_issue to create or update resources in Mcp Jira Stdio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jira Stdio environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | Description format: "markdown" (converts Markdown to ADF), "adf" (use as-is ADF object), "plain" (converts plain text to ADF with basic formatting). Default: "m |
labels | array | — | New labels (replaces existing) |
parent | string | — | New parent issue key (e.g., PROJECT-100). Set to empty string to remove the parent. |
summary | string | — | New summary |
assignee | string | — | New assignee account ID |
issueKey | string | Yes | Issue key to update |
priority | string | — | New priority |
components | array | — | New components (replaces existing) |
description | object | — | New description. Accepts plain text or ADF object. |
returnIssue | boolean | — | When false, skip fetching full issue after update |
Parameters from the server's own tool schema.
This tool modifies existing Jira issues by updating reversible fields (summary, description, priority, assignee, labels, components). These changes can be undone by subsequent updates, making it a Write operation rather than Destructive.
From the tool's definition Tool description states it 'Updates an existing Jira issue' and 'Supports updating summary, description, priority, assignee, labels, and components.' The word 'Updates' indicates modification of existing data.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown). Only specified fields will be updated. It is categorised as a Write tool in the Mcp Jira Stdio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
jira_update_issue accepts 10 parameters: format, labels, parent, summary, assignee, issueKey, priority, components, description, returnIssue. Required: issueKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Jira Stdio MCP server in PolicyLayer and add a rule for jira_update_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 Mcp Jira Stdio. Nothing to install.
jira_update_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_update_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_update_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_update_issue is provided by the Mcp Jira Stdio MCP server (mcp-jira-stdio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →