Delete/reset all indexes for a project (both local and cloud)
AI agents call ambiance_reset_indexes to permanently remove resources in Ambiance MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of data (indexes) without the ability to undo the action. While not a direct data loss (the source code remains), destroying project indexes eliminates the semantic compression and analysis metadata that the Ambiance server relies on, forcing complete re-indexing.
From the tool's definition Tool description explicitly states "Delete/reset all indexes" — a destructive operation that irreversibly removes project indexes stored both locally and in the cloud.
Attacks that exploit this kind of access
Delete/reset all indexes for a project (both local and cloud). It is categorised as a Destructive tool in the Ambiance MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ambiance MCP Server MCP server in PolicyLayer and add a rule for ambiance_reset_indexes: 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 Ambiance MCP Server. Nothing to install.
ambiance_reset_indexes 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 ambiance_reset_indexes 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 ambiance_reset_indexes. 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.
ambiance_reset_indexes is provided by the Ambiance MCP Server MCP server (sbarron/ambiancemcp). 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 →