list_cycles

Retrieve cycles for a specific Linear team

SERVERLinear SOURCE@linear-mcp-server

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/linear/list-cycles.md

WHAT IT DOES

What list_cycles does on Linear

AI agents call list_cycles 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
`type`	string	—	Retrieve the current, previous, next, or all cycles. If no type is provided all cycles in the team will be returned
`teamId`	string	—	The team ID

Parameters from the server's own tool schema.

RISK

Why list_cycles is rated Low

The tool retrieves or queries cycle information; it is a read-only operation that does not create, modify, delete, execute code, or involve financial transactions. The blast radius of misuse is minimal as it only exposes existing data about project cycles.

From the tool's definition Tool name 'list_cycles' and description 'Retrieve cycles for a specific Linear team' indicate a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_cycles 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 list_cycles, this is the rule to start with:

list_cycles Allowed

list_cycles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_cycles": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every list_cycles call is checked against it from then on.

FAQ

Questions about list_cycles

What does the list_cycles tool do? +

Retrieve cycles for a specific Linear team. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.

What parameters does list_cycles accept? +

list_cycles accepts 2 parameters: type, teamId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_cycles? +

Register the Linear MCP server in PolicyLayer and add a rule for list_cycles: 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.

What risk level is list_cycles? +

list_cycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_cycles? +

Yes. Add a rate_limit block to the list_cycles 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 list_cycles completely? +

Set action: deny in the PolicyLayer policy for list_cycles. 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 list_cycles? +

list_cycles 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.

KEEP EXPLORING

More on Linear, and thousands of servers like it.

This server

All 66 Linear tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →