Resize the browser window
AI agents invoke resize_page to trigger actions in BrowserPilot 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 an external operation affecting the browser's state. It doesn't read data, write persistent data, or cause destructive/financial effects, but it does execute a browser-level action. Misuse potential is minimal — at worst it disrupts the viewport/layout, making severity low.
From the tool's definition 'Resize the browser window' — triggers an external browser operation that changes the state of the browser window
Attacks that exploit this kind of access
Resize the browser window. It is categorised as a Execute tool in the BrowserPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BrowserPilot 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 BrowserPilot MCP. Nothing to install.
resize_page 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 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.
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.
resize_page is provided by the BrowserPilot MCP server (sept-7-qi/browserpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →