Curri MCP Server

11 tools. 2 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

2 can modify or destroy data
9 read-only
11 tools total

Community server · catalogue entry verified 05/07/2026

How to control Curri MCP Server ↓

What Curri MCP Server exposes to your agents

Read (9) Write / Execute (1) Destructive / Financial (1)
Critical Risk

The most dangerous Curri MCP Server tools

2 of Curri MCP Server's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Curri MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Curri MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "linear_delete_issue": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

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

Rate limit write operations
{
  "linear_create_issue": {
    "limits": [
      {
        "counter": "linear_create_issue_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "linear_get_cycle": {
    "limits": [
      {
        "counter": "linear_get_cycle_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Curri MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON CURRI →

Instant setup, no code required.

All 11 Curri MCP Server tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Curri MCP Server

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

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

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

The Curri MCP Server server has 1 write tools including linear_create_issue. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Curri MCP Server.

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

11 tools across 3 categories: Destructive, Read, Write. 9 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Curri MCP Server? +

Register the Curri MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Curri MCP Server tool call.

Deterministic rules across all 11 Curri MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

11 Curri MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.