This record as markdown: /tools/linear/linear-convertissuetosubtask.md
What linear_convertIssueToSubtask does on Linear
AI agents use linear_convertIssueToSubtask to create or update resources in Linear, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
issueId | string | — | ID or identifier of the issue to convert (e.g., ABC-123) |
parentIssueId | string | — | ID or identifier of the parent issue (e.g., ABC-456) |
Parameters from the server's own tool schema.
Why linear_convertIssueToSubtask is rated Medium
This tool modifies an existing issue by converting its type/status to a subtask, which is a reversible structural change. It does not delete or destroy data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). It is a Write operation that alters issue metadata and relationships.
From the tool's definition Tool name 'convertIssueToSubtask' and description 'Convert an issue to a subtask' indicate modification of an issue's structure and hierarchy, changing its relationship within the project.
Attacks that exploit this kind of access
The rule that runs linear_convertIssueToSubtask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_convertIssueToSubtask, this is the rule to start with:
linear_convertIssueToSubtask 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_convertIssueToSubtask call is checked against it from then on.
Questions about linear_convertIssueToSubtask
Convert an issue to a subtask. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
linear_convertIssueToSubtask accepts 2 parameters: issueId, parentIssueId. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for linear_convertIssueToSubtask: 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 Linear. Nothing to install.
linear_convertIssueToSubtask 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 linear_convertIssueToSubtask 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 linear_convertIssueToSubtask. 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.
linear_convertIssueToSubtask is provided by the Linear MCP server (@linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue