resize_page · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What resize_page does on Chrome Devtools

AI agents invoke resize_page 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 IT NEEDS A POLICY

Why resize_page needs a policy

Resizing a page is a browser manipulation action that affects the live browser state. It falls under Execute as it triggers an external operation (viewport resize) whose effect depends on the arguments provided. It is not purely Read/Write since it manipulates the browser environment, but the blast radius is low as it only changes display dimensions and is generally reversible.

From the tool's definition Resizes the selected page — triggers a browser viewport/window resize action on a live Chrome browser 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, 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 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. 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 (nimbus21/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

resize_page is one line of Chrome Devtools's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →