List cycles for a specific team.
AI agents call linear_list_cycles to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves cycle data from Linear (a project management platform) for a specific team. It performs no modifications, deletions, or external operations—purely data retrieval. The blast radius of misuse is minimal, as an attacker could only read organizational planning information, not modify projects, delete data, or access sensitive financial/personal information beyond team cycle visibility.
From the tool's definition Tool name 'linear_list_cycles' and description 'List cycles for a specific team' indicate a retrieval operation with no side effects. The verb 'list' is a standard Read operation.
Attacks that exploit this kind of access
List cycles for a specific team. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →