browser_clear_storage
A destructive tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-clear-storage.md
What browser_clear_storage does on Looking Glass
AI agents call browser_clear_storage to permanently remove resources in Looking Glass, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | What to clear |
Parameters from the server's own tool schema.
Why browser_clear_storage is rated Critical
The 'clear_storage' operation implies permanent removal of data that cannot be easily recovered. While the empty description reduces confidence slightly, the semantic context—an AI browser with tools for session management and clearing operations—and the pattern of sibling 'clear' and 'clean' tools strongly suggests this performs irreversible data deletion.
From the tool's definition Tool named 'browser_clear_storage' with no description provided. Based on naming convention and sibling tools (browser_clear_history, browser_clean_slate) on an AI-native browser server, this tool irreversibly deletes or wipes stored browser data…
Attacks that exploit this kind of access
The rule that runs browser_clear_storage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_clear_storage, this is the rule to start with:
browser_clear_storage 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 Looking Glass, apply this rule, and every browser_clear_storage call is checked against it from then on.
Questions about browser_clear_storage
browser_clear_storage is a destructive tool on the Looking Glass MCP server. It is categorised as a Destructive tool in the Looking Glass MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
browser_clear_storage accepts 1 parameter: type. Required: type. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_clear_storage: 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 Looking Glass. Nothing to install.
browser_clear_storage 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 browser_clear_storage 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 browser_clear_storage. 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.
browser_clear_storage is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue