// SCAN REPORT

MCP Local Context

6 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

1 can modify or destroy data

5 read-only

6 tools total

Community server · catalogue entry verified 02/07/2026

How to control MCP Local Context ↓

TOOL MAP

What MCP Local Context exposes to your agents

Read (5) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Local Context tools

Write · Medium build_docs_index Based on the tool name and server context (local documentation with RAG capabilities), 'build_docs_index' most likely builds or rebuilds a search/vector index over local documents.

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

POLICY

How to control MCP Local Context

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

Rate limit write operations

{
  "build_docs_index": {
    "limits": [
      {
        "counter": "build_docs_index_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_local_doc": {
    "limits": [
      {
        "counter": "get_local_doc_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register MCP Local Context — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP LOCAL CONTEXT →

Instant setup, no code required.

FULL CATALOGUE

All 6 MCP Local Context tools

WRITE 1 tools

Write build_docs_index build_docs_index

READ 5 tools

Read get_local_doc get_local_doc Read list_docs_by_type list_docs_by_type Read list_local_docs list_local_docs Read search_local_docs search_local_docs Read semantic_search semantic_search

EXPLORE

Related servers

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

FAQ

Questions about MCP Local Context

How do I prevent bulk modifications through MCP Local Context? +

The MCP Local Context server has 1 write tools including build_docs_index. 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 MCP Local Context.

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

6 tools across 2 categories: Execute, Read. 5 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on MCP Local Context? +

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

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

ENFORCE POLICY ON MCP LOCAL CONTEXT →

Instant setup, no code required.

6 MCP Local Context tools catalogued and risk-classified — across an index of 43,000+ MCP servers.