index_purge

インデックスファイルを全削除します。壊れたインデックスを廃棄して再構築する場合に使います。

Server Search Docs otolab/search-docs
Category Destructive
Risk class Critical
Parameters 00 required

What index_purge does on Search Docs

AI agents call index_purge to permanently remove resources in Search Docs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why index_purge needs a policy

The tool permanently deletes all index files. While this action is potentially recoverable through re-indexing (via the 'init' sibling tool), the index_purge tool itself performs irreversible data deletion.

From the tool's definition Tool description states 'インデックスファイルを全削除します' (deletes all index files). This is an irreversible deletion operation that cannot be undone.

Questions about index_purge

What does the index_purge tool do? +

インデックスファイルを全削除します。壊れたインデックスを廃棄して再構築する場合に使います。. It is categorised as a Destructive tool in the Search Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on index_purge? +

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

What risk level is index_purge? +

index_purge is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit index_purge? +

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

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

index_purge is provided by the Search Docs MCP server (otolab/search-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.