clear_index

Clear the entire index (vector database and metadata).

Server Codebase Contextifier 9000 jarmentor/codebase-contextifier-9000
Category Destructive
Risk class Critical
Parameters 00 required

What clear_index does on Codebase Contextifier 9000

AI agents call clear_index to permanently remove resources in Codebase Contextifier 9000 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_index needs a policy

This tool permanently removes all indexed data from the vector database and metadata stores without the ability to recover it (unless backups exist outside the tool's scope). While not a direct financial or execution risk, it is destructive in that it irreversibly wipes out the semantic search index that the server is built around.

From the tool's definition Tool name is 'clear_index' with description stating it will 'Clear the entire index (vector database and metadata).' The word 'clear' combined with 'entire index' indicates irreversible deletion of all indexed data.

Risk signalsBulk/mass operation — affects multiple targets

Questions about clear_index

What does the clear_index tool do? +

Clear the entire index (vector database and metadata). It is categorised as a Destructive tool in the Codebase Contextifier 9000 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 clear_index? +

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

What risk level is clear_index? +

clear_index 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 clear_index? +

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

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

clear_index is provided by the Codebase Contextifier 9000 MCP server (jarmentor/codebase-contextifier-9000). 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.