Linear MCP Server

32 tools. 17 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

17 can modify or destroy data
15 read-only
32 tools total
Read (15) Write / Execute (15) Destructive / Financial (2)

Financial operations (linear_transferIssue) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Destructive tools (linear_removeIssueLabel) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (linear_addIssueLabel, linear_addIssueToCycle, linear_addIssueToProject) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Block financial tools by default
linear_transferIssue:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
linear_removeIssueLabel:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
linear_addIssueLabel:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
linear_getActiveCycle:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent move money through the Linear MCP Server MCP server? +

Yes. The Linear MCP Server server exposes 1 financial tools including linear_transferIssue. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the Linear MCP Server MCP server? +

Yes. The Linear MCP Server server exposes 1 destructive tools including linear_removeIssueLabel. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Linear MCP Server? +

The Linear MCP Server server has 15 write tools including linear_addIssueLabel, linear_addIssueToCycle, linear_addIssueToProject. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Linear MCP Server MCP server expose? +

32 tools across 4 categories: Destructive, Financial, Read, Write. 15 are read-only. 17 can modify, create, or delete data.

How do I add Intercept to my Linear MCP Server setup? +

One line change. Instead of running the Linear MCP Server server directly, prefix it with Intercept: intercept -c emmett-deen-linear-mcp-server.yaml -- npx -y @emmett-deen/linear-mcp-server. Download a pre-built policy from policylayer.com/policies/emmett-deen-linear-mcp-server and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.