storage_remove_local

Remove a key from localStorage.

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-remove-local.md

WHAT IT DOES

What storage_remove_local does on Mcp Anything

AI agents call storage_remove_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.

RISK

Why storage_remove_local is rated Critical

This tool permanently deletes data from localStorage with no undo capability. While the blast radius is limited to client-side storage (not system-wide or financial), the irreversible nature of deletion and potential loss of user state, preferences, or session data classifies it as Destructive rather than Write. High severity because a compromised agent could systematically wipe application state or user data.

From the tool's definition Tool name 'storage_remove_local' and description 'Remove a key from localStorage' indicate irreversible deletion of stored data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs storage_remove_local safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_remove_local, this is the rule to start with:

storage_remove_local Hidden

storage_remove_local is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "storage_remove_local"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every storage_remove_local call is checked against it from then on.

FAQ

Questions about storage_remove_local

What does the storage_remove_local tool do? +

Remove a key from localStorage. 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_remove_local? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for storage_remove_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_remove_local? +

storage_remove_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_remove_local? +

Yes. Add a rate_limit block to the storage_remove_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_remove_local completely? +

Set action: deny in the PolicyLayer policy for storage_remove_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_remove_local? +

storage_remove_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.

KEEP EXPLORING

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

This server

All 261 Mcp Anything tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →