Switch to a tab in a browser or terminal. Matches by URL substring, then title substring, then index.
AI agents invoke switch_tab to trigger actions in Mcp Desktop. 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 tabs is an active UI control operation that changes the state of a browser or terminal application. It's part of the 'full UI control' trust level described in the server description, and triggers an external operation (changing focus/active tab). While not destructive or financial, it enables navigation that could be a precursor to further automated actions, placing it in Execute rather than Write or Read.
From the tool's definition Switch to a tab in a browser or terminal. Matches by URL substring, then title substring, then index.
Attacks that exploit this kind of access
Switch to a tab in a browser or terminal. Matches by URL substring, then title substring, then index. It is categorised as a Execute tool in the Mcp Desktop MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Desktop MCP server in PolicyLayer and add a rule for switch_tab: 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 Desktop. Nothing to install.
switch_tab 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_tab 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_tab. 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_tab is provided by the Mcp Desktop MCP server (mocha06/mcp-desktop). 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 →