Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown).
AI agents use jira_create_subtask 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 | — | Subtask labels |
summary | string | Yes | Subtask summary/title |
assignee | string | — | Assignee account ID |
priority | string | — | Subtask priority |
components | array | — | Component names |
description | object | — | Subtask description. Accepts plain text or ADF object. |
parentIssueKey | string | Yes | Parent issue key |
Parameters from the server's own tool schema.
This tool creates new data (subtasks) in Jira, which is a reversible operation. It does not execute arbitrary code, delete data irreversibly, or move money. Creating issue subtasks is a standard write operation with moderate blast radius if misused by an AI agent—it could spam the system or clutter projects with unwanted subtasks, but changes can be undone.
From the tool's definition Tool name is 'jira_create_subtask' and description states it 'Creates a subtask under an existing parent issue' with support for setting various fields like priority, assignee, labels, and components.
Attacks that exploit this kind of access
Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown). 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_subtask accepts 8 parameters: format, labels, summary, assignee, priority, components, description, parentIssueKey. Required: summary, parentIssueKey. 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_subtask: 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_subtask 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_subtask 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_subtask. 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_subtask 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 →