List Cache Storage API caches and their entries (see browser_docs)
AI agents call browser_storage_get_cache_storage to retrieve information from Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries cache storage data in the browser's Cache Storage API. It performs read-only operations that list existing caches and their contents. There is no data modification, deletion, code execution, or external effects. The operation is informational only, making it a standard Read category tool with low severity.
From the tool's definition Tool name contains 'get' and description states 'List Cache Storage API caches and their entries', indicating retrieval of stored data without modification or side effects.
Attacks that exploit this kind of access
List Cache Storage API caches and their entries (see browser_docs). It is categorised as a Read tool in the Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_storage_get_cache_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 Browser MCP Server. Nothing to install.
browser_storage_get_cache_storage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_storage_get_cache_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_storage_get_cache_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_storage_get_cache_storage 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 →