Creates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, components, and custom fields. Description format is controlled by the "format" parameter (default: markdown). For required custom fields, supply them via customFields (e.g., { "customfield...
AI agents use jira_create_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 | — | Issue labels |
summary | string | Yes | Issue summary/title |
assignee | string | — | Assignee account ID |
priority | string | — | Issue priority |
issueType | string | Yes | Issue type (e.g., Bug, Story, Task) |
components | array | — | Component names |
projectKey | string | Yes | Project key where the issue will be created |
description | object | — | Issue description. Accepts plain text or ADF object. |
returnIssue | boolean | — | When false, skip fetching full issue after creation |
customFields | object | — | Additional Jira field mappings, e.g. { "customfield_12345": value }. Use for required custom fields. |
Parameters from the server's own tool schema.
This tool creates new data in Jira (a reversible operation). It does not delete, destroy, or move financial resources. While it modifies state, the action is not destructive—issues can be modified or deleted later. It falls clearly into the Write category as it involves creating new records.
From the tool's definition Tool name is 'jira_create_issue' and description states it 'Creates a new Jira issue' with support for setting issue type, priority, assignee, labels, components, and custom fields. Returns the created issue with all details.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Creates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, components, and custom fields. Description format is controlled by the "format" parameter (default: markdown). For required custom fields, supply them via customFields (e.g., { "customfield_12345": { id: "..." } }). Returns the created issue with all details. 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_create_issue accepts 11 parameters: format, labels, summary, assignee, priority, issueType, components, projectKey, description, returnIssue, customFields. Required: summary, issueType, projectKey. 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_create_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_create_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_create_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_create_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_create_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.
jira_create_issue is one line of Mcp Jira Stdio's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →