index_codebase

THE RISK

High Risk

This tool triggers an active operation over the entire codebase — scanning, parsing, and indexing files — and may also regenerate wiki/business pages. It is not a simple read (it writes index data and generated pages) and involves executing a potentially expensive, wide-scope processing pipeline.

From the tool's definition Index or re-index the codebase. Also regenerates deterministic wiki/business pages when the wiki layer is enabled.

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

HOW TO CONTROL INDEX_CODEBASE

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

policy.json

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

index_codebase 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 Reporecall — 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

More Reporecall tools

Destructive clear_index Clear all indexed data Destructive clear_working_memory Clear generated working memory entries from the local managed store. Destructive forget_memory Delete a memory by name. Removes the file and its index entries. Write compact_memories Refresh and compact memory indexes. Falls back to a safe refresh if the compactor is not a Write store_memory Create or update a memory file. The memory will be indexed for future recall. Write wiki_write Create or update a wiki page manually. Use this to persist codebase knowledge that should Read build_stack_tree Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it Read business_context_query Find product areas and business capability pages relevant to a query. Returns business-fac

All 30 Reporecall tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Reporecall → 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the index_codebase tool do? +

Index or re-index the codebase. Also regenerates deterministic wiki/business pages when the wiki layer is enabled. It is categorised as a Execute tool in the Reporecall 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_codebase? +

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

What risk level is index_codebase? +

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

Can I rate-limit index_codebase? +

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

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

index_codebase is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN REPORECALL →

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT INDEX_CODEBASE ON REPORECALL DOES

// THE RISK

// HOW TO CONTROL INDEX_CODEBASE

// EXPLORE