Open a URL in a new tab to present content or enable user interaction with webpages
AI agents invoke open_in_new_tab to trigger actions in Mcp Chrome Tabs. 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.
This tool executes a browser action (opening a new tab to a specified URL), which constitutes an external operation with side effects. An AI agent could misuse this to navigate the user's browser to arbitrary URLs, potentially exposing them to malicious sites or triggering unwanted interactions. It is more than a read or write — it executes a browser-level operation whose effects depend on the URL argument.
From the tool's definition "Open a URL in a new tab" — triggers a browser action that opens an external URL, causing a side effect in the browser environment
Documented attack patterns abuse exactly the kind of access open_in_new_tab gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Chrome Tabs, and nothing reaches the server without passing your rules. This is the rule we recommend for open_in_new_tab:
{
"version": "1",
"default": "deny",
"tools": {
"open_in_new_tab": {
"limits": [
{
"counter": "open_in_new_tab_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} open_in_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.
Free to start. No card required.
Open a URL in a new tab to present content or enable user interaction with webpages. It is categorised as a Execute tool in the Mcp Chrome Tabs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Chrome Tabs MCP server in PolicyLayer and add a rule for open_in_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 Mcp Chrome Tabs. Nothing to install.
open_in_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 open_in_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 open_in_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.
open_in_new_tab is provided by the Mcp Chrome Tabs MCP server (pokutuna/mcp-chrome-tabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Mcp Chrome Tabs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Mcp Chrome Tabs tools catalogued and risk-classified — across an index of 42,500+ MCP servers.