linear_getActiveCycle
Get the currently active cycle for a team
This record as markdown: /tools/linear/linear-getactivecycle.md
What linear_getActiveCycle does on Linear
AI agents call linear_getActiveCycle 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 |
|---|---|---|---|
teamId | string | — | ID of the team to get the active cycle for |
Parameters from the server's own tool schema.
Why linear_getActiveCycle is rated Low
This tool queries and retrieves information about the active cycle for a team. It performs a read-only operation with no side effects, no data modification, and no execution of external operations. The retrieval of cycle status information poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'getActiveCycle' and description 'Get the currently active cycle for a team' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs linear_getActiveCycle 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 linear_getActiveCycle, this is the rule to start with:
linear_getActiveCycle is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every linear_getActiveCycle call is checked against it from then on.
Questions about linear_getActiveCycle
Get the currently active cycle for a team. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
linear_getActiveCycle accepts 1 parameter: teamId. The full parameter table on this page comes from the server's own tool schema.
Register the Linear MCP server in PolicyLayer and add a rule for linear_getActiveCycle: 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.
linear_getActiveCycle 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_getActiveCycle 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_getActiveCycle. 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_getActiveCycle 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.
More on Linear, and thousands of servers like it.
This server
Across the catalogue