reindex_docs · MCP Generix MCP: Risk & Policy

WHAT IT DOES

What reindex_docs does on MCP Generix

AI agents invoke reindex_docs to trigger actions in MCP Generix. 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.

WHY IT NEEDS A POLICY

Why reindex_docs needs a policy

This tool triggers an external operation (fetching from GitHub) and rebuilds the entire index, which involves network I/O and modifying the local ChromaDB index state. It is not purely destructive (data is not permanently lost) but it executes a multi-step external operation that overwrites the existing index.

From the tool's definition Re-fetch and re-index all documents from GitHub. Run this after adding or removing files.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reindex_docs Rate-limited

reindex_docs 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_docs": {
      "limits": [
        {
          "counter": "reindex_docs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Generix, so you can run agents against it safely.

FAQ

Questions about reindex_docs

What does the reindex_docs tool do? +

Re-fetch and re-index all documents from GitHub. Run this after adding or removing files. It is categorised as a Execute tool in the MCP Generix 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_docs? +

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

What risk level is reindex_docs? +

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

Can I rate-limit reindex_docs? +

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

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

reindex_docs is provided by the MCP Generix MCP server (itsphily/mcp_generix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.