Critical Risk →

browser_localstorage_delete

browser_localstorage_delete

How to control browser_localstorage_delete ↓

What browser_localstorage_delete does on Playwright

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

Critical Risk

Why browser_localstorage_delete needs a policy

The name follows the pattern of other browser storage tools on this server (browser_cookie_delete, browser_cookie_clear) which perform destructive operations. Deleting localStorage entries is irreversible within the current session context. Empty description lowers confidence slightly, but the naming convention and sibling tools provide strong contextual evidence.

From the tool's definition Tool name 'browser_localstorage_delete' — 'delete' suffix strongly implies irreversible removal of localStorage data in the browser.

Documented attack patterns abuse exactly the kind of access browser_localstorage_delete gives an agent:

How to control browser_localstorage_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_localstorage_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "browser_localstorage_delete"
  ]
}

browser_localstorage_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Playwright — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_localstorage_delete

What does the browser_localstorage_delete tool do? +

browser_localstorage_delete. It is categorised as a Destructive tool in the Playwright 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 browser_localstorage_delete? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_localstorage_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 Playwright. Nothing to install.

What risk level is browser_localstorage_delete? +

browser_localstorage_delete 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 browser_localstorage_delete? +

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

How do I block browser_localstorage_delete completely? +

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

What MCP server provides browser_localstorage_delete? +

browser_localstorage_delete is provided by the Playwright MCP server (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Playwright tool call.

Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

68 Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.