wavexis_localstorage_clear
Clear all localStorage entries.
This record as markdown: /tools/wavexis-mcp/wavexis-localstorage-clear.md
What wavexis_localstorage_clear does on Pypi:wavexis
AI agents call wavexis_localstorage_clear to permanently remove resources in Pypi:wavexis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wavexis_localstorage_clear is rated Critical
This tool irreversibly deletes data (all localStorage) with no undo mechanism. While the blast radius is scoped to a single browser context's localStorage rather than system-wide, the data loss is complete and unrecoverable. This meets the Destructive threshold: actions that cannot be undone.
From the tool's definition Tool description explicitly states 'Clear all localStorage entries' — a permanent, irreversible deletion of all stored local data in the browser context.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs wavexis_localstorage_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_localstorage_clear, this is the rule to start with:
wavexis_localstorage_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 Pypi:wavexis, apply this rule, and every wavexis_localstorage_clear call is checked against it from then on.
Questions about wavexis_localstorage_clear
Clear all localStorage entries. It is categorised as a Destructive tool in the Pypi:wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_localstorage_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 Pypi:wavexis. Nothing to install.
wavexis_localstorage_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_localstorage_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_localstorage_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_localstorage_clear is provided by the Pypi: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 Pypi:wavexis, and thousands of servers like it.
Across the catalogue