linear_update_cycle

A write tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/linear-update-cycle.md

WHAT IT DOES

What linear_update_cycle does on Allmcp

AI agents use linear_update_cycle to create or update resources in Allmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allmcp environment.

RISK

Why linear_update_cycle is rated Medium

The 'update' verb in the tool name indicates data modification rather than deletion, retrieval, or execution of arbitrary logic. Updating a cycle in Linear is reversible (can be changed again), placing it in Write category.

From the tool's definition Tool name 'linear_update_cycle' indicates modification of a cycle entity in Linear (issue tracking system). The verb 'update' explicitly denotes a write operation that modifies existing data. Description is empty, which slightly reduces confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs linear_update_cycle safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_update_cycle, this is the rule to start with:

linear_update_cycle Rate-limited

linear_update_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_update_cycle": {
      "limits": [
        {
          "counter": "linear_update_cycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_update_cycle call is checked against it from then on.

FAQ

Questions about linear_update_cycle

What does the linear_update_cycle tool do? +

linear_update_cycle is a write tool on the All MCP server. It is categorised as a Write tool in the Allmcp 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_update_cycle? +

Register the All MCP server in PolicyLayer and add a rule for linear_update_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 Allmcp. Nothing to install.

What risk level is linear_update_cycle? +

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

Can I rate-limit linear_update_cycle? +

Yes. Add a rate_limit block to the linear_update_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_update_cycle completely? +

Set action: deny in the PolicyLayer policy for linear_update_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_update_cycle? +

linear_update_cycle is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on All, and thousands of servers like it.

This server

All 501 All tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →