Removes all indexed data for a specific file from both Redis and SQLite.
AI agents call remove_indexed_file 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 performs an irreversible deletion operation ('Removes') that cannot be undone. While the data being deleted is indexed/cached code context rather than production data, the loss of all indexed data for a file means cached semantic search results and code context cannot be recovered without re-indexing. The deletion affects both Redis and SQLite storage layers, representing a permanent data loss.
From the tool's definition Tool name 'remove_indexed_file' combined with description stating it 'Removes all indexed data for a specific file from both Redis and SQLite' indicates irreversible deletion of indexed data.
Attacks that exploit this kind of access
Removes all indexed data for a specific file from both Redis and SQLite. 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 remove_indexed_file: 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.
remove_indexed_file 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 remove_indexed_file 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 remove_indexed_file. 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.
remove_indexed_file 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 →