New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_window_switch

Switch focus to a different browser window.

SERVERTermux Browser Pilot SOURCEsalviz/termux-browser-pilot
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/salviz-termux-browser-pilot/browser-window-switch.md

What browser_window_switch does on Termux Browser Pilot

AI agents invoke browser_window_switch to trigger actions in Termux Browser Pilot. 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.

Why browser_window_switch is rated High

Switching browser window focus is a browser action/operation that changes the state of a running browser session. It falls under Execute as it triggers an external operation (browser window management) whose effects depend on which window is targeted. It's not merely reading data, nor does it write/destroy data directly, but it performs an active browser automation action.

From the tool's definition Switch focus to a different browser window

Questions about browser_window_switch

What does the browser_window_switch tool do? +

Switch focus to a different browser window. It is categorised as a Execute tool in the Termux Browser Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_window_switch? +

Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_window_switch: 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 Termux Browser Pilot. Nothing to install.

What risk level is browser_window_switch? +

browser_window_switch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_window_switch? +

Yes. Add a rate_limit block to the browser_window_switch 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.

How do I block browser_window_switch completely? +

Set action: deny in the PolicyLayer policy for browser_window_switch. 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.

What MCP server provides browser_window_switch? +

browser_window_switch is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Termux Browser Pilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Termux Browser Pilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.