get_storage_key_for_frame
Get the storage key for a specific frame. Args: frame_id: Frame ID to get storage key for Returns: Storage key for the frame
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-storage-key-for-frame.md
What get_storage_key_for_frame does on Chrome Devtools
AI agents call get_storage_key_for_frame 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 get_storage_key_for_frame is rated Low
This tool retrieves metadata about a frame's storage key without creating, modifying, deleting, or executing any operations. It has no side effects and returns information only. Despite being part of a DevTools suite with other tools capable of destructive operations (clear_all_cookies, clear_storage_for_origin), this specific tool is purely informational and falls squarely within the Read category.
From the tool's definition Tool description states 'Get the storage key for a specific frame' with a return value of 'Storage key for the frame'. The verb 'Get' and the action of retrieving/querying a storage key without modification indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_storage_key_for_frame 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 get_storage_key_for_frame, this is the rule to start with:
get_storage_key_for_frame 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 get_storage_key_for_frame call is checked against it from then on.
Questions about get_storage_key_for_frame
Get the storage key for a specific frame. Args: frame_id: Frame ID to get storage key for Returns: Storage key for the frame. 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 get_storage_key_for_frame: 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.
get_storage_key_for_frame 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 get_storage_key_for_frame 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 get_storage_key_for_frame. 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.
get_storage_key_for_frame 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