puppeteer_hover · Puppeteer MCP Server MCP: Risk & Policy

WHAT IT DOES

What puppeteer_hover does on Puppeteer MCP Server

AI agents invoke puppeteer_hover 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_hover needs a policy

Hovering is a browser action that executes within an automated browser session. While it seems benign, it can trigger JavaScript event listeners (mouseenter, mouseover) with arbitrary side effects. It fits Execute as it triggers external browser operations whose effects depend on arguments (which element is hovered).

From the tool's definition "Hover an element on the page" — triggers a browser interaction (mouseover/hover event) that can cause side effects such as revealing hidden menus, triggering JavaScript event handlers, or initiating dynamic content loads.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

puppeteer_hover Rate-limited

puppeteer_hover 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_hover": {
      "limits": [
        {
          "counter": "puppeteer_hover_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_hover

What does the puppeteer_hover tool do? +

Hover an element on the page. 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_hover? +

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

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

Can I rate-limit puppeteer_hover? +

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

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

puppeteer_hover 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.