browser_tab_new
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-tab-new.md
What browser_tab_new does on Looking Glass
AI agents invoke browser_tab_new to trigger actions in Looking Glass. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | URL to open in new tab |
Parameters from the server's own tool schema.
Why browser_tab_new is rated High
This tool triggers browser state changes (creating new tabs), which is an external operation whose effects depend on context and arguments (which URL to load, etc.). While not immediately destructive or financial, it qualifies as Execute category because it performs an action rather than reading data.
From the tool's definition Tool name 'browser_tab_new' indicates browser control. Sibling tools like 'browser_click', 'browser_close', and context of 'AI-native browser for agents' confirm this server exposes browser automation capabilities.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs browser_tab_new safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_tab_new, this is the rule to start with:
browser_tab_new 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 Looking Glass, apply this rule, and every browser_tab_new call is checked against it from then on.
Questions about browser_tab_new
browser_tab_new is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_tab_new accepts 1 parameter: url. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_tab_new: 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 Looking Glass. Nothing to install.
browser_tab_new 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 browser_tab_new 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 browser_tab_new. 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.
browser_tab_new is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue