index_repository

THE RISK

High Risk

Why index_repository needs a policy

Indexing a repository involves scanning the filesystem, parsing code files, building data structures, and writing cache/index files. This is more than a read — it triggers an external operation (indexing pipeline) and writes cached index data. It does not delete or move money, but it executes a non-trivial process that modifies stored state (the index/cache).

From the tool's definition 'Index or re-index the repository to enable all context-manager tools. Uses cached index if files haven\'t changed'

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

POLICY

How to control index_repository

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_repository": {
      "limits": [
        {
          "counter": "index_repository_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

index_repository stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register MCP Context Manager — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Context Manager tools

Destructive clear_cache Clear the cached index for a repository. Useful if cache becomes corrupted or you want to Destructive delete_symbol 🗑️ NEW: Delete a symbol (Serena-inspired). Remove function/class/etc cleanly. Symbol-leve Execute build_dependency_graph 🚀 NEW: Build dependency graph for the entire codebase. Call this once after indexing to e Write insert_after_symbol ✏️ NEW: Insert code after a symbol (Serena-inspired). Symbol-level editing without reading Write replace_symbol ✏️ NEW: Replace a symbol with new code (Serena-inspired). Surgical precision editing. Repl Read find_similar Find code similar to a given symbol. Useful for discovering related implementations, simil Read find_symbol ⭐ PREFERRED FOR SYMBOLS: Use this INSTEAD OF Grep when looking for specific functions, cla Read find_symbol_references 🔍 NEW: Find all places where a symbol is used (Serena-inspired). Shows usages across all

All 21 MCP Context Manager tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MCP Context Manager → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about index_repository

What does the index_repository tool do? +

🔧 REQUIRED FIRST STEP: Index or re-index the repository to enable all context-manager tools. Uses cached index if files haven\. It is categorised as a Execute tool in the MCP Context Manager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on index_repository? +

Register the MCP Context Manager MCP server in PolicyLayer and add a rule for index_repository: 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 MCP Context Manager. Nothing to install.

What risk level is index_repository? +

index_repository is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit index_repository? +

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

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

index_repository is provided by the MCP Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Context Manager tool call.

Start from MCP Context Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →