Create a new page in an existing browser
AI agents invoke new_page to trigger actions in MCP Playwright 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.
While new_page itself does not read, write, delete, or move money, it is an operational action that triggers external browser behavior. Classification as Execute is appropriate because it initiates a programmatic operation on an external system (browser) whose consequences depend on agent-directed arguments and follow-up actions.
From the tool's definition Tool description states it 'Create a new page in an existing browser' and is part of a browser automation server enabling 'actions like navigation, clicking, typing' through natural language interfaces.
Attacks that exploit this kind of access
Create a new page in an existing browser. It is categorised as a Execute tool in the MCP Playwright Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Playwright Server MCP server in PolicyLayer and add a rule for 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 MCP Playwright Server. Nothing to install.
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 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 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.
new_page is provided by the MCP Playwright Server MCP server (mostafaraafat91/mcp-playwright-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 →