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 SOURCEnikolai-vysotskyi/trace-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/reindex.md

WHAT IT DOES

What reindex does on Trace

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.

RISK

Why reindex is rated High

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).'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reindex safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reindex, this is the rule to start with:

reindex Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every reindex call is checked against it from then on.

FAQ

Questions about reindex

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.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →