Remove the index for a directory. Deletes all file records, vector embeddings, and the directory entry from the database. When to use this tool: - User wants to remove a directory from the search index - Cleaning up old or irrelevant indexed content - Freeing database space by removing unused ind...
AI agents call delete_index to permanently remove resources in Directory Indexer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes indexed data including file records and vector embeddings. While the actual files on disk are preserved, the deletion of database records and embeddings cannot be undone and represents a permanent loss of indexed knowledge. An agent misusing this could remove access to critical indexed content.
From the tool's definition Tool description explicitly states it "Deletes all file records, vector embeddings, and the directory entry from the database" with no restore mechanism described. The operation removes data irreversibly from multiple systems (SQLite, Qdrant vector database).
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access delete_index gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Directory Indexer, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_index:
{
"version": "1",
"default": "deny",
"hide": [
"delete_index"
]
}delete_index disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove the index for a directory. Deletes all file records, vector embeddings, and the directory entry from the database. When to use this tool: - User wants to remove a directory from the search index - Cleaning up old or irrelevant indexed content - Freeing database space by removing unused indexes How it works: - Removes all file records for the specified directory from SQLite - Deletes corresponding vector embeddings from Qdrant - Removes the directory entry from the directories table - Does NOT delete the actual files on disk Examples: - Remove old project: directory_path=. It is categorised as a Destructive tool in the Directory Indexer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Directory Indexer MCP server in PolicyLayer and add a rule for delete_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 Directory Indexer. Nothing to install.
delete_index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_index is provided by the Directory Indexer MCP server (peteretelej/directory-indexer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Directory Indexer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Directory Indexer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.