wavexis_indexeddb_clear
Clear an IndexedDB object store.
This record as markdown: /tools/wavexis-mcp/wavexis-indexeddb-clear.md
What wavexis_indexeddb_clear does on Wavexis
AI agents call wavexis_indexeddb_clear to permanently remove resources in Wavexis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wavexis_indexeddb_clear is rated Critical
Clearing an IndexedDB object store permanently removes all records in that store without undo capability. This is a destructive operation that destroys data. While the blast radius is limited to the current browser context and application, the permanent data loss and inability to recover the deleted records justifies 'high' severity. Confidence is high because the action description is explicit and unambiguous.
From the tool's definition Tool name contains 'clear' and description states 'Clear an IndexedDB object store' — this irreversibly deletes data stored in the browser's IndexedDB.
Attacks that exploit this kind of access
The rule that runs wavexis_indexeddb_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_indexeddb_clear, this is the rule to start with:
wavexis_indexeddb_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_indexeddb_clear call is checked against it from then on.
Questions about wavexis_indexeddb_clear
Clear an IndexedDB object store. It is categorised as a Destructive tool in the Wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_indexeddb_clear: 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 Wavexis. Nothing to install.
wavexis_indexeddb_clear 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 wavexis_indexeddb_clear 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 wavexis_indexeddb_clear. 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.
wavexis_indexeddb_clear is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
Across the catalogue