AI agents call linear_list_cycles to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation only. It queries and returns cycles (likely sprint/project cycles) for a specified Linear team. No data is created, modified, deleted, or any external operations are triggered. The operation is purely informational with no side effects.
From the tool's definition The tool name 'linear_list_cycles' contains the verb 'list', which retrieves or queries data. The description 'List cycles for a Linear team' explicitly indicates a read operation that retrieves cycle information without modifying any state.
Documented attack patterns abuse exactly the kind of access linear_list_cycles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_list_cycles:
{
"version": "1",
"default": "deny",
"tools": {
"linear_list_cycles": {}
}
}linear_list_cycles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List cycles for a Linear team. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage 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 Sage 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 Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.