update_issue_estimate · Linear MCP: Risk & Policy

WHAT IT DOES

What update_issue_estimate does on Linear

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

WHY IT NEEDS A POLICY

Why update_issue_estimate needs a policy

This tool modifies existing data (an issue's estimate field) in a reversible manner. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial). Update operations that change metadata like estimates are Write-category tools.

From the tool's definition Tool description states 'Update the estimate of an existing issue' - a modification operation. The server supports 'full CRUD operations' including updates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_issue_estimate Rate-limited

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

FAQ

Questions about update_issue_estimate

What does the update_issue_estimate tool do? +

Update the estimate of an existing issue in Linear. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_issue_estimate? +

Register the Linear MCP server in PolicyLayer and add a rule for update_issue_estimate: 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.

What risk level is update_issue_estimate? +

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

Can I rate-limit update_issue_estimate? +

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

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

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