pageindex_local_reindex_document · Pageindex Local MCP

WHAT IT DOES

What pageindex_local_reindex_document does on Pageindex Local

AI agents use pageindex_local_reindex_document to create or update resources in Pageindex Local — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pageindex Local environment.

WHY IT NEEDS A POLICY

Why pageindex_local_reindex_document needs a policy

This tool regenerates/overwrites the index for an existing document. It modifies existing data (the document's index) but does so reversibly — the document itself is not deleted and the index can be regenerated again. This is a Write operation rather than Execute because it's a defined pipeline action on a known document, not arbitrary code execution.

From the tool's definition Re-run local PageIndex generation for an existing document

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pageindex_local_reindex_document Rate-limited

pageindex_local_reindex_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pageindex_local_reindex_document": {
      "limits": [
        {
          "counter": "pageindex_local_reindex_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about pageindex_local_reindex_document

What does the pageindex_local_reindex_document tool do? +

Re-run local PageIndex generation for an existing document. It is categorised as a Write tool in the Pageindex Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pageindex_local_reindex_document? +

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

What risk level is pageindex_local_reindex_document? +

pageindex_local_reindex_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pageindex_local_reindex_document? +

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

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

pageindex_local_reindex_document is provided by the Pageindex Local MCP server (jamesbubenik/pageindex-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.