Launch a new browser instance
AI agents invoke launch_browser 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.
This tool triggers execution of an external process (browser launch) whose effects depend on arguments and subsequent tool calls. While launching a browser itself is not destructive or financial, it is an Execute action because it initiates an external operation that could be chained with other tools (navigate, click, type_text) to perform arbitrary browser-based actions.
From the tool's definition Tool 'launch_browser' launches a new browser instance, which is an external operation that initiates a new process.
Attacks that exploit this kind of access
Launch a new browser instance. 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 launch_browser: 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.
launch_browser 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 launch_browser 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 launch_browser. 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.
launch_browser 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 →