Delete a specific cache from Cache Storage (see browser_docs)
AI agents call browser_storage_delete_cache to permanently remove resources in Browser MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes cached data from the browser's Cache Storage API. This is destructive because cache deletion cannot be undone and may disrupt application functionality, lose user data, or break offline capabilities.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific cache from Cache Storage' — this is an irreversible removal of stored data.
Attacks that exploit this kind of access
Delete a specific cache from Cache Storage (see browser_docs). It is categorised as a Destructive tool in the Browser MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_storage_delete_cache: 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 Browser MCP Server. Nothing to install.
browser_storage_delete_cache 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_storage_delete_cache 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_storage_delete_cache. 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_storage_delete_cache is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →