puppeteer_click · Puppeteer MCP: Risk & Policy

WHAT IT DOES

What puppeteer_click does on Puppeteer

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

Clicking in a browser context is an Execute-level action because its effects are entirely dependent on what element is clicked — it could trigger anything from navigation to form submission to financial transactions. The description is empty, so confidence is reduced, but the Puppeteer context and sibling tools strongly imply browser automation.

From the tool's definition Tool name 'puppeteer_click' on a Puppeteer server with sibling tools including puppeteer_navigate, puppeteer_evaluate, puppeteer_fill — all browser automation actions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

puppeteer_click Rate-limited

puppeteer_click 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_click": {
      "limits": [
        {
          "counter": "puppeteer_click_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, so you can run agents against it safely.

FAQ

Questions about puppeteer_click

What does the puppeteer_click tool do? +

puppeteer_click. It is categorised as a Execute tool in the 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_click? +

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

What risk level is puppeteer_click? +

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

Can I rate-limit puppeteer_click? +

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

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

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