linear_convertIssueToSubtask · Linear MCP Server MCP

WHAT IT DOES

What linear_convertIssueToSubtask does on Linear MCP Server

AI agents use linear_convertIssueToSubtask to create or update resources in Linear MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Server environment.

WHY IT NEEDS A POLICY

Why linear_convertIssueToSubtask needs a policy

This tool modifies existing data (an issue's type/status) in a reversible manner by changing how an issue is classified within the hierarchy. It does not delete data (which would be Destructive), execute arbitrary code (Execute), nor does it move money (Financial). It fits the Write category as it updates/transforms data state.

From the tool's definition The tool converts an issue to a subtask, modifying the structural relationship and properties of an existing issue within Linear's project management system. The description explicitly states it performs a conversion operation, which transforms data state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_convertIssueToSubtask Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_convertIssueToSubtask": {
      "limits": [
        {
          "counter": "linear_convertissuetosubtask_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 Linear MCP Server, so you can run agents against it safely.

FAQ

Questions about linear_convertIssueToSubtask

What does the linear_convertIssueToSubtask tool do? +

Convert an issue to a subtask. It is categorised as a Write tool in the Linear MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on linear_convertIssueToSubtask? +

Register the Linear MCP Server 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 MCP Server. Nothing to install.

What risk level is linear_convertIssueToSubtask? +

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

Can I rate-limit linear_convertIssueToSubtask? +

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.

How do I block linear_convertIssueToSubtask completely? +

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.

What MCP server provides linear_convertIssueToSubtask? +

linear_convertIssueToSubtask is provided by the Linear MCP Server MCP server (wkoutre/linear-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.