Claude Context

7 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
5 read-only
7 tools total

Community server · catalogue entry verified 10/06/2026

How to control Claude Context ↓

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

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

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

Deny destructive operations
{
  "clear_index": {
    "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
{
  "edit": {
    "limits": [
      {
        "counter": "edit_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "directory_tree": {
    "limits": [
      {
        "counter": "directory_tree_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 Claude Context — 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 CLAUDE CONTEXT →

Free to start. No card required.

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

Can an AI agent delete data through the Claude Context MCP server? +

Yes. The Claude Context server exposes 1 destructive tools including clear_index. 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 Claude Context? +

The Claude Context server has 1 write tools including edit. 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 Claude Context.

How many tools does the Claude Context MCP server expose? +

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

How do I enforce a policy on Claude Context? +

Register the Claude Context 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 Claude Context tool call.

Deterministic rules across all 7 Claude Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

7 Claude Context 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.