Delete the SQLite workspace index file.
AI agents call clear_index to permanently remove resources in Syntax Map — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes the SQLite index file used for cross-file searches and caching. While the index can be rebuilt via 'index_workspace', the current indexed data is irreversibly lost, causing downstream tools (find_indexed_definition, find_indexed_references, get_index_status) to lose their cached results.
From the tool's definition Tool description states: 'Delete the SQLite workspace index file.' The use of 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete the SQLite workspace index file. It is categorised as a Destructive tool in the Syntax Map MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Syntax Map 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 Syntax Map. 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 Syntax Map MCP server (kht6163/syntax-map-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 →