clear_storage_for_origin
Clear storage data for a specific origin. Args: origin: Security origin to clear storage for storage_types: Comma-separated list of storage types to clear (cookies, local_storage, indexeddb, cache_storage, etc.) Returns: Success status of the clear operation
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/clear-storage-for-origin.md
What clear_storage_for_origin does on Chrome Devtools
AI agents call clear_storage_for_origin to permanently remove resources in Chrome Devtools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_storage_for_origin is rated Critical
This tool permanently removes user data without recovery options. While not financial in nature, it qualifies as Destructive because it irreversibly deletes data that cannot be restored.
From the tool's definition clear_storage_for_origin irreversibly deletes storage data (cookies, local_storage, indexeddb, cache_storage) for a specified origin. The description explicitly states it 'clears' storage with no undo mechanism.
Attacks that exploit this kind of access
The rule that runs clear_storage_for_origin safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_storage_for_origin, this is the rule to start with:
clear_storage_for_origin 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 Chrome Devtools, apply this rule, and every clear_storage_for_origin call is checked against it from then on.
Questions about clear_storage_for_origin
Clear storage data for a specific origin. Args: origin: Security origin to clear storage for storage_types: Comma-separated list of storage types to clear (cookies, local_storage, indexeddb, cache_storage, etc.) Returns: Success status of the clear operation. It is categorised as a Destructive tool in the Chrome Devtools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for clear_storage_for_origin: 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 Chrome Devtools. Nothing to install.
clear_storage_for_origin 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 clear_storage_for_origin 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 clear_storage_for_origin. 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.
clear_storage_for_origin is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue