browser_localstorage_clear

A destructive tool on the Playwright MCP server.

SERVERPlaywright MCP SOURCEalialobidm/playwright-mcp
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/alialobidm-playwright-mcp/browser-localstorage-clear.md

What browser_localstorage_clear does on Playwright MCP

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

Why browser_localstorage_clear is rated Critical

This tool permanently deletes all localStorage entries for the current domain, which cannot be undone. localStorage often contains user preferences, session tokens, authentication state, or application data critical to functionality. An AI agent misusing this could destroy user data or break application state irreversibly.

From the tool's definition Tool name 'browser_localstorage_clear' indicates irreversible deletion of localStorage data. The 'clear' suffix denotes removal/destruction.

Questions about browser_localstorage_clear

What does the browser_localstorage_clear tool do? +

browser_localstorage_clear is a destructive tool on the Playwright MCP server. It is categorised as a Destructive tool in the Playwright MCP 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_clear? +

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

What risk level is browser_localstorage_clear? +

browser_localstorage_clear 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_clear? +

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

How do I block browser_localstorage_clear completely? +

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

What MCP server provides browser_localstorage_clear? +

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

More on Playwright, 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 Playwright'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.