Clear the company document search index for the default project and branch from config. Clears the entire branch directory: {reposBasePath}/{defaultProject}/{defaultBranch}
AI agents call clear_index to permanently remove resources in Claude Context MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'clear_index' operation irreversibly deletes the entire search index for a branch directory. While it doesn't delete source code repositories, it destroys indexed metadata that cannot be easily recovered without re-indexing. This is a destructive action that cannot be undone without rebuilding the index from scratch.
From the tool's definition Tool clears and removes the entire branch directory: {reposBasePath}/{defaultProject}/{defaultBranch}, which irreversibly deletes indexed data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear the company document search index for the default project and branch from config. Clears the entire branch directory: {reposBasePath}/{defaultProject}/{defaultBranch}. It is categorised as a Destructive tool in the Claude Context MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Context 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 Claude Context MCP. 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 Claude Context MCP server (sahinrasit/ibtech-mcp-claude-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →