storage_clear_local

Clear all localStorage data.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/storage-clear-local.md

What storage_clear_local does on Mcp Anything

AI agents call storage_clear_local to permanently remove resources in Mcp Anything, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why storage_clear_local is rated Critical

This tool permanently erases all browser localStorage data with no undo mechanism. While scoped to client-side storage rather than backend databases, the irreversible nature and potential to destroy user session state, preferences, authentication tokens, and application data justifies the Destructive category. The 'clear all' scope amplifies risk compared to targeted deletion.

From the tool's definition storage_clear_local: 'Clear all localStorage data.' — uses 'clear' which indicates irreversible deletion of all localStorage without granular control or recovery option.

Risk signalsBulk/mass operation — affects multiple targets

Questions about storage_clear_local

What does the storage_clear_local tool do? +

Clear all localStorage data. It is categorised as a Destructive tool in the Mcp Anything MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on storage_clear_local? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for storage_clear_local: 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 Mcp Anything. Nothing to install.

What risk level is storage_clear_local? +

storage_clear_local is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit storage_clear_local? +

Yes. Add a rate_limit block to the storage_clear_local 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.

How do I block storage_clear_local completely? +

Set action: deny in the PolicyLayer policy for storage_clear_local. 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.

What MCP server provides storage_clear_local? +

storage_clear_local is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Anything, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Anything's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.