<tool> <purpose>Permanently removes all indexed data for a codebase</purpose> <when_to_use> <scenario>Clear stale data before reindexing after major code changes</scenario> <scenario>Remove old indexed codebases no longer needed</scenario> <scenario>Fix corrupted index causing search issues</scen...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Deepcontext server.
Free to start. No card required.
AI agents may call clear_index to permanently remove or destroy resources in Deepcontext. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call clear_index in a loop, permanently destroying resources in Deepcontext. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"clear_index"
]
}See the full Deepcontext policy for all 4 tools.
These attack patterns abuse exactly the kind of access clear_index gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
<tool> <purpose>Permanently removes all indexed data for a codebase</purpose> <when_to_use> <scenario>Clear stale data before reindexing after major code changes</scenario> <scenario>Remove old indexed codebases no longer needed</scenario> <scenario>Fix corrupted index causing search issues</scenario> </when_to_use> <parameters> <parameter name="codebase_path" required="false"> <type>string</type> <description>ABSOLUTE path to the codebase to clear</description> <examples> <valid>/Users/name/project</valid> <valid>/home/user/code/repo</valid> <invalid>.</invalid> <invalid>../project</invalid> <invalid>relative/path</invalid> </examples> <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation> <optional_behavior>Omit to clear ALL indexed codebases (use with caution)</optional_behavior> </parameter> </parameters> <warnings> <warning>Destructive operation. All search capabilities lost until reindexing</warning> </warnings> </tool>. It is categorised as a Destructive tool in the Deepcontext MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deepcontext 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 Deepcontext. Nothing to install.
clear_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 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.
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.
clear_index is provided by the Deepcontext MCP server (@wildcard-ai/deepcontext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Deepcontext tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.