This record as markdown: /tools/browser/set-active-tab.md
What set_active_tab does on Browser
AI agents invoke set_active_tab to trigger actions in Browser. 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 set_active_tab is rated High
Switching the active tab is a browser control action with side effects (changes UI state and focus), placing it in the Execute category. While not destructive or data-modifying, it triggers an external operation in the browser. Misuse could redirect agent attention or disrupt user workflow, but blast radius is relatively limited.
From the tool's definition Set active tab (tab id) — triggers a browser action that changes the active/focused tab
Attacks that exploit this kind of access
The rule that runs set_active_tab safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_active_tab, this is the rule to start with:
set_active_tab stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Browser, apply this rule, and every set_active_tab call is checked against it from then on.
Questions about set_active_tab
Set active tab (tab id). It is categorised as a Execute tool in the Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browser MCP server in PolicyLayer and add a rule for set_active_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 Browser. Nothing to install.
set_active_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 set_active_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 set_active_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.
set_active_tab is provided by the Browser MCP server (mcp-server-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Browser, and thousands of servers like it.
Across the catalogue