override_storage_quota
Override storage quota for a specific origin. Args: origin: Security origin to override quota for quota_size_mb: New quota size in MB (optional, removes override if not provided) Returns: Quota override status
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/override-storage-quota.md
What override_storage_quota does on Chrome Devtools
AI agents invoke override_storage_quota to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why override_storage_quota is rated High
This tool modifies browser/system configuration by overriding storage quota limits for a given origin. It's not a simple data write (it changes operational parameters), nor is it destructive (it can be reversed by removing the override). It triggers an external browser operation via the Chrome DevTools Protocol, fitting the Execute category.
From the tool's definition Override storage quota for a specific origin... New quota size in MB (optional, removes override if not provided)
Attacks that exploit this kind of access
The rule that runs override_storage_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 override_storage_quota, this is the rule to start with:
override_storage_quota stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 override_storage_quota call is checked against it from then on.
Questions about override_storage_quota
Override storage quota for a specific origin. Args: origin: Security origin to override quota for quota_size_mb: New quota size in MB (optional, removes override if not provided) Returns: Quota override status. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for override_storage_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.
override_storage_quota is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the override_storage_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 override_storage_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.
override_storage_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.
Across the catalogue