connect-browser-with-ws · TgeBrowser MCP Server MCP

WHAT IT DOES

What connect-browser-with-ws does on TgeBrowser MCP Server

AI agents invoke connect-browser-with-ws to trigger actions in TgeBrowser 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.

WHY IT NEEDS A POLICY

Why connect-browser-with-ws needs a policy

This tool establishes a WebSocket/CDP connection to a browser instance, enabling subsequent automation actions. It is an Execute-category tool because it triggers an external operation (connecting to a live browser via Chrome DevTools Protocol) whose effects depend on the target browser and enable further automated interactions. It does not merely read data, nor does it destructively delete anything.

From the tool's definition Connect to an opened browser via WebSocket CDP URL... Must be called before using any automation tools (navigate, screenshot, click, fill-input, etc.)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect-browser-with-ws Rate-limited

connect-browser-with-ws 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect-browser-with-ws": {
      "limits": [
        {
          "counter": "connect-browser-with-ws_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TgeBrowser MCP Server, so you can run agents against it safely.

FAQ

Questions about connect-browser-with-ws

What does the connect-browser-with-ws tool do? +

Connect to an opened browser via WebSocket CDP URL (obtained from open-browser result). Must be called before using any automation tools (navigate, screenshot, click, fill-input, etc.). It is categorised as a Execute tool in the TgeBrowser 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 connect-browser-with-ws? +

Register the TgeBrowser MCP Server MCP server in PolicyLayer and add a rule for connect-browser-with-ws: 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 TgeBrowser MCP Server. Nothing to install.

What risk level is connect-browser-with-ws? +

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

Can I rate-limit connect-browser-with-ws? +

Yes. Add a rate_limit block to the connect-browser-with-ws 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 connect-browser-with-ws completely? +

Set action: deny in the PolicyLayer policy for connect-browser-with-ws. 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 connect-browser-with-ws? +

connect-browser-with-ws is provided by the TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.