This record as markdown: /tools/browser/new-tab.md
What new_tab does on Browser
AI agents invoke new_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 new_tab is rated High
Creating a new tab with a specified URL is an Execute-class action because it triggers an external browser operation whose effects depend on the URL argument. While opening a tab alone is less severe than code execution, in the context of an MCP server for 'browser automation,' this tool can be chained with execute_script and other siblings to perform complex automated actions.
From the tool's definition Tool opens a new browser tab with a URL. Combined with sibling tools like execute_script, this is part of a browser automation toolkit that can trigger external operations and navigate to arbitrary destinations.
Attacks that exploit this kind of access
The rule that runs new_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 new_tab, this is the rule to start with:
new_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 new_tab call is checked against it from then on.
Questions about new_tab
New tab (url). 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 new_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.
new_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 new_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 new_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.
new_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