Add an issue to a cycle
AI agents use linear_addIssueToCycle 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.
This tool creates or modifies a relationship between an issue and a cycle within Linear's project management system. The action is reversible (the issue can be removed from the cycle), and it does not delete data or execute arbitrary code. It falls under the Write category as it modifies project state without destructive or executable side effects.
From the tool's definition Tool name 'linear_addIssueToCycle' and description 'Add an issue to a cycle' indicate a modification operation that associates an issue with a project cycle, changing issue metadata reversibly.
Attacks that exploit this kind of access
Add an issue to a cycle. 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.
Register the Linear MCP Server 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 MCP Server. 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 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.
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 →