linear_update_milestone · Linearapp MCP: Risk & Policy

WHAT IT DOES

What linear_update_milestone does on Linearapp

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

WHY IT NEEDS A POLICY

Why linear_update_milestone needs a policy

This tool modifies an existing milestone's attributes (dates, names, descriptions, etc.) in Linear's project management system. Updates are reversible through subsequent corrections, distinguishing this from destructive operations. The impact is limited to milestone metadata rather than code execution or financial transactions.

From the tool's definition Tool name 'linear_update_milestone' and description 'Update an existing milestone in Linear' indicate modification of existing data. The verb 'update' is a reversible write operation that changes milestone properties without deletion or destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_update_milestone Rate-limited

linear_update_milestone 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_milestone": {
      "limits": [
        {
          "counter": "linear_update_milestone_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 Linearapp, so you can run agents against it safely.

FAQ

Questions about linear_update_milestone

What does the linear_update_milestone tool do? +

Update an existing milestone in Linear. It is categorised as a Write tool in the Linearapp 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_milestone? +

Register the Linearapp MCP server in PolicyLayer and add a rule for linear_update_milestone: 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 Linearapp. Nothing to install.

What risk level is linear_update_milestone? +

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

Can I rate-limit linear_update_milestone? +

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

Set action: deny in the PolicyLayer policy for linear_update_milestone. 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_milestone? +

linear_update_milestone is provided by the Linearapp MCP server (mcp-server-linearapp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.