switches to a specific window by handle
AI agents invoke switch_to_window to trigger actions in Selenium 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.
Switching browser windows is a browser automation action that changes the active execution context. While it doesn't directly read or write data, it directs subsequent browser operations to a different window, making it an Execute-category action. Misuse could redirect agent actions to unintended browser contexts, but blast radius is moderate since it doesn't directly cause data loss or financial harm.
From the tool's definition "switches to a specific window by handle" — controls browser window focus/context via Selenium WebDriver
Attacks that exploit this kind of access
switches to a specific window by handle. It is categorised as a Execute tool in the Selenium MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Selenium MCP Server MCP server in PolicyLayer and add a rule for switch_to_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 Selenium MCP Server. Nothing to install.
switch_to_window 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 switch_to_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.
Set action: deny in the PolicyLayer policy for switch_to_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.
switch_to_window is provided by the Selenium MCP Server MCP server (jyothishkumarav/selenium-mcp-server-python). 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 →