browser_resize_window · Browser MCP Server MCP

WHAT IT DOES

What browser_resize_window does on Browser MCP Server

AI agents invoke browser_resize_window to trigger actions in Browser MCP Server. 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 browser_resize_window needs a policy

Resizing the browser window triggers an external browser operation that changes the browser's state. It's not a simple read, nor does it create/modify persistent data or delete anything. It executes a browser action (window resize) whose effect depends on the arguments provided (dimensions). Severity is low as the blast radius is minimal — it only affects the visual/layout state of the browser session.

From the tool's definition Resize the browser window (useful for testing responsiveness)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_resize_window Rate-limited

browser_resize_window 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": {
    "browser_resize_window": {
      "limits": [
        {
          "counter": "browser_resize_window_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 Browser MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_resize_window

What does the browser_resize_window tool do? +

Resize the browser window (useful for testing responsiveness) (see browser_docs). It is categorised as a Execute tool in the Browser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_resize_window? +

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

What risk level is browser_resize_window? +

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

Can I rate-limit browser_resize_window? +

Yes. Add a rate_limit block to the browser_resize_window 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 browser_resize_window completely? +

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

browser_resize_window is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

browser_resize_window is one line of Browser MCP Server'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 →