Cambia el tamaño de la ventana a una resolución aleatoria.
AI agents invoke randomize_viewport to trigger actions in MCP Selenium WebDriver. 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.
This tool modifies the browser window/viewport size, which is a browser action with external effects on the running browser session. It fits Execute as it triggers an operation on the browser. Severity is low since misuse only affects viewport dimensions with no data loss or financial impact.
From the tool's definition Cambia el tamaño de la ventana a una resolución aleatoria (Changes window size to a random resolution) — triggers a browser action modifying viewport state
Attacks that exploit this kind of access
Cambia el tamaño de la ventana a una resolución aleatoria. It is categorised as a Execute tool in the MCP Selenium WebDriver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for randomize_viewport: 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 MCP Selenium WebDriver. Nothing to install.
randomize_viewport 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 randomize_viewport 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 randomize_viewport. 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.
randomize_viewport is provided by the MCP Selenium WebDriver MCP server (nixon-suarez/mcp-selenium-webdriver). 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 →