track_cache_storage
Enable or disable cache storage tracking for an origin. Args: origin: Security origin to track enable: Whether to enable or disable tracking Returns: Tracking status
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/track-cache-storage.md
What track_cache_storage does on Chrome Devtools
AI agents call track_cache_storage to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why track_cache_storage is rated Low
Although 'enable or disable' appears in the description, the core function is tracking (observing) cache storage, not modifying application data. Cache storage tracking is a DevTools monitoring feature analogous to enabling breakpoints or performance profiling — it configures observation, not data mutation.
From the tool's definition 'Enable or disable cache storage tracking for an origin' — the tool monitors/observes cache storage state without modifying it; tracking is a read operation that captures telemetry or monitoring data.
Attacks that exploit this kind of access
The rule that runs track_cache_storage 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 track_cache_storage, this is the rule to start with:
track_cache_storage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every track_cache_storage call is checked against it from then on.
Questions about track_cache_storage
Enable or disable cache storage tracking for an origin. Args: origin: Security origin to track enable: Whether to enable or disable tracking Returns: Tracking status. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for track_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 Chrome Devtools. Nothing to install.
track_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 track_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 track_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.
track_cache_storage 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.
This server
Across the catalogue