puppeteer_connect_active_tab

THE RISK

High Risk

Why puppeteer_connect_active_tab needs a policy

Connecting to an active Chrome instance with remote debugging gives the tool full control over an existing browser session, including access to authenticated sessions, cookies, and the ability to perform arbitrary browser actions. This is an execution-level capability since it enables control of external browser operations whose effects depend on what is subsequently done with the connection.

From the tool's definition Connect to an existing Chrome instance with remote debugging enabled

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

POLICY

How to control puppeteer_connect_active_tab

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

policy.json

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

puppeteer_connect_active_tab 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 Puppeteer 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 Puppeteer MCP Server tools

Execute puppeteer_evaluate Execute JavaScript in the browser console Execute puppeteer_navigate Navigate to a URL Execute puppeteer_click Click an element on the page Execute puppeteer_fill Fill out an input field Execute puppeteer_hover Hover an element on the page Execute puppeteer_select Select an element on the page with Select tag Read puppeteer_screenshot Take a screenshot of the current page or a specific element

All 8 Puppeteer 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 Puppeteer 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 puppeteer_connect_active_tab

What does the puppeteer_connect_active_tab tool do? +

Connect to an existing Chrome instance with remote debugging enabled. It is categorised as a Execute tool in the Puppeteer 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 puppeteer_connect_active_tab? +

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

What risk level is puppeteer_connect_active_tab? +

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

Can I rate-limit puppeteer_connect_active_tab? +

Yes. Add a rate_limit block to the puppeteer_connect_active_tab 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 puppeteer_connect_active_tab completely? +

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

puppeteer_connect_active_tab is provided by the Puppeteer MCP Server MCP server (merajmehrabi/puppeteer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Puppeteer MCP Server tool call.

Start from Puppeteer 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 →