Open a new browser tab and switch to it.
AI agents invoke browser_new_tab to trigger actions in Daytona Playwright MCP Server. 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 performs a browser action that executes external operations (tab management in a cloud sandbox Chrome instance). While it does not directly read, write, delete data, or move money, it is an Execute category tool because it triggers browser state changes and enables subsequent navigation/interaction.
From the tool's definition Tool opens a new browser tab and switches to it. This is a browser control action that triggers external operations in a Chrome browser running in a cloud sandbox.
Attacks that exploit this kind of access
Open a new browser tab and switch to it. It is categorised as a Execute tool in the Daytona Playwright MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Daytona Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_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 Daytona Playwright MCP Server. Nothing to install.
browser_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 browser_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 browser_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.
browser_new_tab is provided by the Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-mcp-server). 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 →