This record as markdown: /tools/linear/linear-addissuetocycle.md
What linear_addIssueToCycle does on Linear
AI agents use linear_addIssueToCycle 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 |
|---|---|---|---|
cycleId | string | — | ID of the cycle to add the issue to |
issueId | string | — | ID or identifier of the issue to add to the cycle |
Parameters from the server's own tool schema.
Why linear_addIssueToCycle is rated Medium
This tool modifies issue state by associating it with a cycle, but the change is reversible (the issue can be removed from the cycle later). It is not a deletion, financial transaction, or arbitrary code execution. The severity is medium because misuse could disrupt project planning workflows, but the blast radius is limited to issue-cycle associations within a single project management system.
From the tool's definition Tool name 'addIssueToCycle' and description 'Add an issue to a cycle' indicate a state-modifying operation that assigns an issue to a project cycle, which is a reversible change to issue metadata.
Attacks that exploit this kind of access
The rule that runs linear_addIssueToCycle 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_addIssueToCycle, this is the rule to start with:
linear_addIssueToCycle 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_addIssueToCycle call is checked against it from then on.
Questions about linear_addIssueToCycle
Add an issue to a cycle. 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_addIssueToCycle accepts 2 parameters: cycleId, issueId. 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_addIssueToCycle: 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_addIssueToCycle 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_addIssueToCycle 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_addIssueToCycle. 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_addIssueToCycle 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