AI agents invoke puppeteer_hover to trigger actions in MCP Puppeteer Linux 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.
Hovering is a browser action that can trigger JavaScript event handlers (mouseover, mouseenter) with potentially dynamic side effects. While typically benign, it executes real browser interactions in a live session. It falls under Execute as it triggers external operations whose effects depend on which element is targeted. Severity is low because hovering alone rarely causes irreversible or high-impact changes.
From the tool's definition 'Hover an element on the page' — triggers a browser interaction (mouseover/hover event) on a live browser session
Documented attack patterns abuse exactly the kind of access puppeteer_hover gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Puppeteer Linux Server, and nothing reaches the server without passing your rules. This is the rule we recommend for puppeteer_hover:
{
"version": "1",
"default": "deny",
"tools": {
"puppeteer_hover": {
"limits": [
{
"counter": "puppeteer_hover_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Hover an element on the page. It is categorised as a Execute tool in the MCP Puppeteer Linux Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Puppeteer Linux 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 MCP Puppeteer Linux Server. Nothing to install.
puppeteer_hover is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
puppeteer_hover is provided by the MCP Puppeteer Linux Server MCP server (phialsbasement/mcp-puppeteer-linux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Puppeteer Linux Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 MCP Puppeteer Linux Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.