This record as markdown: /tools/linear/linear-getcycles.md
What linear_getCycles does on Linear
AI agents call linear_getCycles to retrieve information from Linear without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of cycles to return (default: 25) |
teamId | string | — | ID of the team to get cycles for (optional) |
Parameters from the server's own tool schema.
Why linear_getCycles is rated Low
This tool retrieves and lists cycles from Linear (a project management system) without modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The low severity reflects minimal risk—an AI agent misusing this tool would only gain visibility into cycle data, not cause destructive or financial harm.
From the tool's definition Tool name 'linear_getCycles' with description 'Get a list of all cycles' indicates retrieval/query of cycle data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs linear_getCycles 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_getCycles, this is the rule to start with:
linear_getCycles is read-only, so it stays allowed. 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_getCycles call is checked against it from then on.
Questions about linear_getCycles
Get a list of all cycles. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getCycles accepts 2 parameters: limit, teamId. 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_getCycles: 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_getCycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the linear_getCycles 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_getCycles. 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_getCycles 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