// MCP TOOL REFERENCE

reindex

Trigger (re)indexing of the project or a subdirectory. Mutates the local index (SQLite). Use after major file changes; for single-file updates prefer register_edit instead. The optional

ServerTrace
CategoryExecute

How to control reindex ↓

WHAT REINDEX ON TRACE DOES

AI agents invoke reindex to trigger actions in Trace. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

This tool triggers an indexing operation that mutates a local SQLite database. It executes a potentially long-running process that modifies internal state (the index). While it doesn't delete user source code, it irreversibly overwrites the existing index data.

From the tool's definition 'Trigger (re)indexing of the project or a subdirectory. Mutates the local index (SQLite).'

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

HOW TO CONTROL REINDEX

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

policy.json

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

reindex 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 Trace — 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 Trace tools

Destructive delete_corpus Remove a saved corpus (manifest + packed body). Returns JSON: { deleted: bool, name }. Destructive remove_dead_code Safely remove a dead symbol from its file. Verifies the symbol is actually dead (multi-sig Destructive repair_index Apply a targeted repair to the local SQLite index. Modes: drop-orphans (delete embedding r Destructive apply_codemod Bulk regex find-and-replace across files. Dry-run by default — first call shows preview, s Write change_signature Change a function/method signature (add/remove/rename/reorder parameters) and update all c Write embed_repo Precompute and cache symbol embeddings for semantic / hybrid search. Embeddings are also c Write unpin Remove a ranking pin by target. Pass either symbol_id (for a pinned symbol) or file_path ( Write build_corpus Pack a slice of project context into a persistent corpus on disk so future query_corpus ca

All 178 Trace 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 Trace → 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 reindex tool do? +

Trigger (re)indexing of the project or a subdirectory. Mutates the local index (SQLite). Use after major file changes; for single-file updates prefer register_edit instead. The optional. It is categorised as a Execute tool in the Trace MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reindex? +

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

What risk level is reindex? +

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

Can I rate-limit reindex? +

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

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

reindex is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Trace tool call.

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

GOVERN TRACE →

Free to start. No card required.

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

reindex

// WHAT REINDEX ON TRACE DOES

// THE RISK

// HOW TO CONTROL REINDEX

// EXPLORE