reindex_wiki

Rebuild the FTS5 search index from scratch.

SERVERAgent Store SOURCEchrisluersen/agent-store

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/agent-store/reindex-wiki.md

WHAT IT DOES

What reindex_wiki does on Agent Store

AI agents invoke reindex_wiki to trigger actions in Agent Store. 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_wiki is rated High

This tool rebuilds a full-text search index from scratch, which is an operation that executes a rebuild process. While it doesn't delete user data, it does perform a potentially long-running, resource-intensive operation that overwrites the existing index entirely. It's most accurately Execute since it triggers an external/internal operation (index rebuild) whose effects depend on the current state of the data.

From the tool's definition Rebuild the FTS5 search index from scratch

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reindex_wiki safely

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

reindex_wiki Rate-limited

reindex_wiki 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_wiki": {
      "limits": [
        {
          "counter": "reindex_wiki_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 Agent Store, apply this rule, and every reindex_wiki call is checked against it from then on.

FAQ

Questions about reindex_wiki

What does the reindex_wiki tool do? +

Rebuild the FTS5 search index from scratch. It is categorised as a Execute tool in the Agent Store 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_wiki? +

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

What risk level is reindex_wiki? +

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

Can I rate-limit reindex_wiki? +

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

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

reindex_wiki is provided by the Agent Store MCP server (chrisluersen/agent-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Store, and thousands of servers like it.

This server

All 19 Agent Store 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 →