resize_page · Chrome DevTools MCP: Risk & Policy

WHAT IT DOES

What resize_page does on Chrome DevTools MCP

AI agents invoke resize_page to trigger actions in Chrome DevTools MCP. 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 IT NEEDS A POLICY

Why resize_page needs a policy

Resizing a browser page is an external operation that modifies the state of a live browser session. It has no direct data read/write or destructive implications, but it does execute a browser action that changes the environment. Severity is low as the blast radius of resizing a page is minimal.

From the tool's definition 'Resizes the selected page' — triggers a browser/viewport action affecting a live Chrome session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resize_page Rate-limited

resize_page 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resize_page": {
      "limits": [
        {
          "counter": "resize_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome DevTools MCP, so you can run agents against it safely.

FAQ

Questions about resize_page

What does the resize_page tool do? +

Resizes the selected page. It is categorised as a Execute tool in the Chrome DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on resize_page? +

Register the Chrome DevTools MCP server in PolicyLayer and add a rule for resize_page: 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 MCP. Nothing to install.

What risk level is resize_page? +

resize_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit resize_page? +

Yes. Add a rate_limit block to the resize_page 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.

How do I block resize_page completely? +

Set action: deny in the PolicyLayer policy for resize_page. 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.

What MCP server provides resize_page? +

resize_page is provided by the Chrome DevTools MCP server (shay5555-gif/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.