Removes all indexed data from both Redis and SQLite, resetting the index.
AI agents call clear_all_indexed_data to permanently remove resources in Code Context Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes all indexed code context data across multiple storage systems (Redis and SQLite). The action cannot be undone and would cause complete loss of the indexed codebase context, disrupting the core functionality of the Code Context Manager for all users. This qualifies as Destructive rather than Write because the deletion is irreversible and represents a total reset of system state.
From the tool's definition Tool description states it 'Removes all indexed data from both Redis and SQLite, resetting the index.' The verb 'removes' combined with 'all indexed data' indicates irreversible deletion of the entire index.
Attacks that exploit this kind of access
Removes all indexed data from both Redis and SQLite, resetting the index. It is categorised as a Destructive tool in the Code Context Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Code Context Manager MCP server in PolicyLayer and add a rule for clear_all_indexed_data: 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 Code Context Manager. Nothing to install.
clear_all_indexed_data 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_all_indexed_data 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_all_indexed_data. 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_all_indexed_data is provided by the Code Context Manager MCP server (theraaz/code-context-manager-mcp). 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 →