refresh_index

THE RISK

High Risk

Re-indexing triggers an external operation that scans and processes the codebase to rebuild an index. This is an Execute-category action as it runs an indexing process whose scope depends on arguments (full vs incremental). It is not purely destructive (existing data is rebuilt, not deleted), not a read (it modifies the index state), and not a simple write.

From the tool's definition Re-index the codebase. Supports full re-index or incremental mode.

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

HOW TO CONTROL REFRESH_INDEX

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

policy.json

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

refresh_index 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 Codebase Context — 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 Codebase Context tools

Write remember CALL IMMEDIATELY when user explicitly asks to remember/record something.\n\n Read detect_circular_dependencies Analyze the import graph to detect circular dependencies between files. Read get_codebase_health Get actionable codebase health signals from the latest index. Returns the highest-risk fil Read get_codebase_metadata Get codebase metadata including framework information, dependencies, architecture patterns Read get_indexing_status Get current indexing status: state, statistics, and progress. Read get_memory Retrieves team conventions, architectural decisions, and known gotchas.\n Read get_style_guide Query style guide rules and architectural patterns from project documentation. Read get_symbol_references Find concrete references to a symbol in indexed chunks. Returns total usageCount and top u

All 11 Codebase Context 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 Codebase Context → 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 refresh_index tool do? +

Re-index the codebase. Supports full re-index or incremental mode. It is categorised as a Execute tool in the Codebase Context MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_index? +

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

What risk level is refresh_index? +

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

Can I rate-limit refresh_index? +

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

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

refresh_index is provided by the Codebase Context MCP server (patricksys/codebase-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codebase Context tool call.

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

GOVERN CODEBASE CONTEXT →

Free to start. No card required.

11 Codebase Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT REFRESH_INDEX ON CODEBASE CONTEXT DOES

// THE RISK

// HOW TO CONTROL REFRESH_INDEX

// EXPLORE