AI agents invoke browser_resize to trigger actions in Playwright 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.
Resizing a browser window is a browser automation action that changes the state of an active session. It falls under Execute as it triggers an external operation (browser window manipulation). The blast radius is low since it only affects viewport dimensions and cannot directly cause data loss or financial harm, but it is part of a broader automation capability.
From the tool's definition 'Resize the browser window' — triggers a browser action that modifies the state of a running browser session
Documented attack patterns abuse exactly the kind of access browser_resize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_resize:
{
"version": "1",
"default": "deny",
"tools": {
"browser_resize": {
"limits": [
{
"counter": "browser_resize_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_resize 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.
Free to start. No card required.
Resize the browser window. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_resize: 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 Playwright MCP. Nothing to install.
browser_resize 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 browser_resize 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 browser_resize. 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.
browser_resize is provided by the Playwright MCP server (korwabs/playwright-record-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Playwright MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.