linear_archiveIssue · Linear MCP Server MCP: Risk & Policy

WHAT IT DOES

What linear_archiveIssue does on Linear MCP Server

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

WHY IT NEEDS A POLICY

Why linear_archiveIssue needs a policy

Archiving modifies issue state and removes it from active view, making it a Write operation. It's not fully Destructive because archiving is conventionally reversible in Linear and similar systems. The severity is medium because an agent could archive many issues inappropriately, disrupting workflows, but the action can be undone.

From the tool's definition Tool name is 'linear_archiveIssue' with description 'Archive an issue'. Archiving is a state change that hides/disables an issue but is reversible—issues can typically be unarchived in project management systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linear_archiveIssue Rate-limited

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

FAQ

Questions about linear_archiveIssue

What does the linear_archiveIssue tool do? +

Archive an issue. It is categorised as a Write tool in the Linear MCP 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_archiveIssue? +

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

What risk level is linear_archiveIssue? +

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

Can I rate-limit linear_archiveIssue? +

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

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

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