List Linear cycles
AI agents call linear_list_cycles to retrieve information from Curri MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries cycles from a Linear workspace without creating, modifying, deleting, or executing any side effects. It falls squarely into the Read category. Severity is low because listing data poses minimal risk—the blast radius of misuse is confined to information disclosure.
From the tool's definition Tool name 'linear_list_cycles' and description 'List Linear cycles' indicate a retrieval/query operation with no modification of data. The verb 'list' is a read-only action.
Attacks that exploit this kind of access
List Linear cycles. It is categorised as a Read tool in the Curri MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Curri MCP Server MCP server in PolicyLayer and add a rule for linear_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 Curri MCP Server. Nothing to install.
linear_list_cycles 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_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.
Set action: deny in the PolicyLayer policy for linear_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.
linear_list_cycles is provided by the Curri MCP Server MCP server (teamcurri/mcp-linear). 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 →