Open a new browser page (tab) (see browser_docs)
AI agents invoke browser_new_page to trigger actions in Browser 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 initiates browser control operations that can have side effects depending on how they are chained with other browser tools. While opening a tab itself is not destructive or financial, it is an Execute action because it programmatically controls external browser behavior.
From the tool's definition Tool opens a new browser page/tab, which is a browser automation action that triggers external operations. The description states it "open[s] a new browser page (tab)" - an action that executes browser control commands.
Attacks that exploit this kind of access
Open a new browser page (tab) (see browser_docs). It is categorised as a Execute tool in the Browser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_new_page: 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 MCP Server. Nothing to install.
browser_new_page 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_page 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_page. 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_page is provided by the Browser MCP Server MCP server (madebytokens/browser-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 →