Set the browser window size.
AI agents invoke set_window_size to trigger actions in SeleniumMCP. 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.
Setting the browser window size is a browser action that affects the state of an active browser session. It fits the Execute category as it triggers an external operation (resizing the browser window). The blast radius is low since it only affects display/layout and has no data or financial implications.
From the tool's definition 'Set the browser window size' — modifies the state of a running browser session, triggering an external browser operation
Attacks that exploit this kind of access
Set the browser window size. It is categorised as a Execute tool in the SeleniumMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Selenium MCP server in PolicyLayer and add a rule for set_window_size: 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 SeleniumMCP. Nothing to install.
set_window_size 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 set_window_size 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 set_window_size. 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.
set_window_size is provided by the Selenium MCP server (lokii0911/seleniummcp). 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 →