get_storage_usage_and_quota
Get storage usage and quota information for an origin. Args: origin: Security origin to check storage for Returns: Storage usage and quota information in bytes
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-storage-usage-and-quota.md
What get_storage_usage_and_quota does on Chrome Devtools
AI agents call get_storage_usage_and_quota 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_usage_and_quota is rated Low
This tool queries and returns storage metrics for a given origin without modifying, executing, or destructing any data. It is purely informational and has no side effects beyond reading statistics. The low severity reflects that storage quota information is non-sensitive metadata that does not directly expose user data or enable harmful actions.
From the tool's definition Tool description states it 'Get[s] storage usage and quota information' and 'Returns: Storage usage and quota information in bytes'. The verb 'get' and the absence of any modification language indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_storage_usage_and_quota 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_usage_and_quota, this is the rule to start with:
get_storage_usage_and_quota 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_usage_and_quota call is checked against it from then on.
Questions about get_storage_usage_and_quota
Get storage usage and quota information for an origin. Args: origin: Security origin to check storage for Returns: Storage usage and quota information in bytes. 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_usage_and_quota: 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_usage_and_quota 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_usage_and_quota 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_usage_and_quota. 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_usage_and_quota 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