trigger_reindex

THE RISK

High Risk

Why trigger_reindex needs a policy

This tool executes a reindexing operation on the codebase, which is a side-effecting computational action triggered by the agent. It is not a simple read (no data retrieval), not a reversible write (it modifies existing index state), and not destructive (no deletion). The operation itself is triggered/executed based on arguments (scope parameter), fitting the Execute category.

From the tool's definition Tool description states 'Trigger a reindex of the codebase' and 'Supports incremental (changed files only) or full mode' — this triggers an external operation (reindexing) whose effects depend on the scope argument provided.

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

POLICY

How to control trigger_reindex

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

policy.json

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

trigger_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 CodeGraph — 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 CodeGraph tools

Destructive decay_and_prune Run temporal memory maintenance: decay relevance scores for old entities and optionally pr Execute query_graph Run a raw Cypher query against the code graph. Use with caution - read-only queries only. Write ingest_conversation Ingest a multi-turn conversation into the knowledge graph. Runs the full episodic pipeline Write store_entity Store an entity in the knowledge graph. Deduplicates by text+type — if an entity with the Write store_fact Extract entities and relationships from natural language text using an LLM, then store the Write store_relationship Store a relationship between two entities in the knowledge graph. Entities are referenced Write add Ingest any content into the knowledge graph. Accepts file paths (PDF, DOCX, HTML, CSV, Write resolve_entities Run on-demand entity resolution (deduplication) on the knowledge graph. Uses 3-tier matchi

All 18 CodeGraph 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 CodeGraph → 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 trigger_reindex

What does the trigger_reindex tool do? +

Trigger a reindex of the codebase. Supports incremental (changed files only) or full mode. If no scope is specified, re-indexes all active projects. It is categorised as a Execute tool in the CodeGraph MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_reindex? +

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

What risk level is trigger_reindex? +

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

Can I rate-limit trigger_reindex? +

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

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

trigger_reindex is provided by the CodeGraph MCP server (phoenixrr2113/codebase-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CodeGraph tool call.

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

CHECK YOUR STACK →