Critical Risk →

linear_archiveTeam

Archive a team

How to control linear_archiveTeam ↓

AI agents call linear_archiveTeam to permanently remove resources in Linear — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Archiving a team is effectively irreversible in practice — it removes the team from active use, hides it from normal views, and likely affects all associated issues, projects, and members. This constitutes a destructive action with a high blast radius since entire teams and their associated data would be impacted.

From the tool's definition Archive a team

Documented attack patterns abuse exactly the kind of access linear_archiveTeam gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Linear, and nothing reaches the server without passing your rules. This is the rule we recommend for linear_archiveTeam:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "linear_archiveTeam"
  ]
}

linear_archiveTeam disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Linear — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the linear_archiveTeam tool do? +

Archive a team. It is categorised as a Destructive tool in the Linear MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on linear_archiveTeam? +

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

linear_archiveTeam is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit linear_archiveTeam? +

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

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

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

Enforce policy on every Linear tool call.

Deterministic rules across all 182 Linear tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

182 Linear tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.