create_websocket_connection

THE RISK

High Risk

Why create_websocket_connection needs a policy

Creating a WebSocket connection to a browser automation framework (Puppeteer/Playwright) opens a persistent channel through which an AI agent could execute arbitrary browser actions, run scripts, navigate pages, exfiltrate data, or interact with authenticated sessions.

From the tool's definition 'Create WebSocket connection for Puppeteer/Playwright' — establishes a live browser automation connection enabling arbitrary browser control via Puppeteer/Playwright

Documented attack patterns abuse exactly the kind of access create_websocket_connection gives an agent:

POLICY

How to control create_websocket_connection

PolicyLayer is an MCP gateway — it sits between your AI agents and Browserless MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_websocket_connection:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_websocket_connection": {
      "limits": [
        {
          "counter": "create_websocket_connection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

create_websocket_connection 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.

Create a free account and register Browserless MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Browserless MCP Server tools

Execute execute_browserql Execute BrowserQL GraphQL queries Execute execute_function Execute custom JavaScript function in browser context Execute initialize_browserless Initialize connection to Browserless instance Execute run_performance_audit Run Lighthouse performance audit Execute download_files Handle file downloads Execute unblock Bypass bot detection and anti-scraping measures Execute export_page Export webpage with resources Execute generate_pdf Generate PDF from URL or HTML content

All 16 Browserless MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Browserless MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_websocket_connection

What does the create_websocket_connection tool do? +

Create WebSocket connection for Puppeteer/Playwright. It is categorised as a Execute tool in the Browserless MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_websocket_connection? +

Register the Browserless MCP Server MCP server in PolicyLayer and add a rule for create_websocket_connection: 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 Browserless MCP Server. Nothing to install.

What risk level is create_websocket_connection? +

create_websocket_connection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_websocket_connection? +

Yes. Add a rate_limit block to the create_websocket_connection 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.

How do I block create_websocket_connection completely? +

Set action: deny in the PolicyLayer policy for create_websocket_connection. 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.

What MCP server provides create_websocket_connection? +

create_websocket_connection is provided by the Browserless MCP Server MCP server (lizzard-solutions/browserless-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Browserless MCP Server tool call.

Start from Browserless MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →