Get a specific Linear cycle
AI agents call linear_get_cycle 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 information about a specific cycle from Linear's issue tracking system. It performs no side effects, creates no data, executes no code, and deletes nothing. It is a straightforward data retrieval operation with minimal security risk—the worst case being unauthorized access to cycle metadata that is typically project-visible information.
From the tool's definition Tool name 'linear_get_cycle' with description 'Get a specific Linear cycle' indicates a retrieval operation. The verb 'get' and the absence of any modification, deletion, or execution language confirm this is a read-only query.
Attacks that exploit this kind of access
Get a specific Linear cycle. 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_get_cycle: 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_get_cycle 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_get_cycle 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_get_cycle. 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_get_cycle 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 →