linear_manage_cycle · Linear MCP Integration Server MCP

WHAT IT DOES

What linear_manage_cycle does on Linear MCP Integration Server

AI agents use linear_manage_cycle to create or update resources in Linear MCP Integration Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear MCP Integration Server environment.

WHY IT NEEDS A POLICY

Why linear_manage_cycle needs a policy

The tool appears to manage cycles (sprints/iterations) in Linear, which typically involves creating, modifying, or reassigning cycles—reversible write operations. While the empty description reduces confidence, the context of Linear project management and sibling write tools (create_issue, bulk_update_status) suggests this performs data modifications rather than reads or irreversible deletions.

From the tool's definition Tool name 'linear_manage_cycle' and sibling tools like 'linear_bulk_update_status' and 'linear_create_issue' indicate write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_manage_cycle Rate-limited

linear_manage_cycle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linear_manage_cycle": {
      "limits": [
        {
          "counter": "linear_manage_cycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linear MCP Integration Server, so you can run agents against it safely.

FAQ

Questions about linear_manage_cycle

What does the linear_manage_cycle tool do? +

linear_manage_cycle. It is categorised as a Write tool in the Linear MCP Integration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on linear_manage_cycle? +

Register the Linear MCP Integration Server MCP server in PolicyLayer and add a rule for linear_manage_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 Linear MCP Integration Server. Nothing to install.

What risk level is linear_manage_cycle? +

linear_manage_cycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit linear_manage_cycle? +

Yes. Add a rate_limit block to the linear_manage_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.

How do I block linear_manage_cycle completely? +

Set action: deny in the PolicyLayer policy for linear_manage_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.

What MCP server provides linear_manage_cycle? +

linear_manage_cycle is provided by the Linear MCP Integration Server MCP server (skspade/mcp-linear-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.