puppeteer_select · Steel Puppeteer MCP: Risk & Policy

WHAT IT DOES

What puppeteer_select does on Steel Puppeteer

AI agents invoke puppeteer_select to trigger actions in Steel Puppeteer. 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 dropdown element is a browser action that causes a state change in the page (fires change/input events, may trigger navigation or form submission side effects). It falls under Execute as it performs an interactive browser operation whose consequences depend on which element and value are targeted.

From the tool's definition 'Select an element on the page with Select tag' — triggers a DOM interaction (selecting a dropdown option) in a live browser environment

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 Steel Puppeteer, 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 Steel Puppeteer 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 Steel Puppeteer 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 Steel Puppeteer. 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 Steel Puppeteer MCP server (rdvo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.