wavexis_cache_storage_delete
Delete a Cache Storage cache.
This record as markdown: /tools/wavexis-mcp/wavexis-cache-storage-delete.md
What wavexis_cache_storage_delete does on Wavexis
AI agents call wavexis_cache_storage_delete 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_cache_storage_delete is rated Critical
Cache Storage deletion removes data that cannot be recovered. Although the blast radius is limited to the origin's cache (not cross-origin), an LLM agent misusing this tool could destroy legitimate application caches, breaking offline functionality or cached assets. This fits the Destructive category (irreversible data removal) rather than Write (reversible modification).
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a Cache Storage cache' — this is an irreversible removal operation on browser storage.
Attacks that exploit this kind of access
The rule that runs wavexis_cache_storage_delete 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_cache_storage_delete, this is the rule to start with:
wavexis_cache_storage_delete 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_cache_storage_delete call is checked against it from then on.
Questions about wavexis_cache_storage_delete
Delete a Cache Storage cache. 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_cache_storage_delete: 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_cache_storage_delete 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_cache_storage_delete 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_cache_storage_delete. 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_cache_storage_delete 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