puppeteer_select · Puppeteer MCP Server MCP: Risk & Policy

WHAT IT DOES

What puppeteer_select does on Puppeteer MCP Server

AI agents invoke puppeteer_select to trigger actions in Puppeteer 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 puppeteer_select needs a policy

Selecting a value in a <select> element is a browser interaction that modifies page/form state and can trigger JavaScript event handlers (onChange, etc.), potentially causing navigation or data submission. This is an Execute-level action within a browser automation context, not a simple read, and its effects depend on the arguments provided.

From the tool's definition 'Select an element on the page with Select tag' — interacts with a live browser DOM element, triggering potential form state changes and downstream effects

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

puppeteer_select Rate-limited

puppeteer_select 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": {
    "puppeteer_select": {
      "limits": [
        {
          "counter": "puppeteer_select_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 Puppeteer MCP Server, so you can run agents against it safely.

FAQ

Questions about puppeteer_select

What does the puppeteer_select tool do? +

Select an element on the page with Select tag. 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_select? +

Register the Puppeteer MCP Server MCP server in PolicyLayer and add a rule for puppeteer_select: 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_select? +

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

Can I rate-limit puppeteer_select? +

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

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

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