browser_hover
A execute tool on the Playwright MCP server.
This record as markdown: /tools/alialobidm-playwright-mcp/browser-hover.md
What browser_hover does on Playwright MCP
AI agents invoke browser_hover to trigger actions in Playwright MCP. 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 browser_hover is rated High
The tool name 'browser_hover' strongly suggests it simulates a mouse hover action on a web page element. Browser automation hover actions are Execute-category operations as they trigger external browser interactions (e.g., revealing tooltips, dropdown menus, triggering JavaScript events). The description is empty, which lowers confidence, but the tool name and server context make this classification reasonable.
From the tool's definition Tool name 'browser_hover' on a browser automation server (Playwright MCP) that provides 'browser automation capabilities' and allows LLMs to 'interact with web pages'.
Attacks that exploit this kind of access
The rule that runs browser_hover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_hover, this is the rule to start with:
browser_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Playwright MCP, apply this rule, and every browser_hover call is checked against it from then on.
Questions about browser_hover
browser_hover is a execute tool on the Playwright MCP server. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_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 Playwright MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_hover is provided by the Playwright MCP server (alialobidm/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Playwright, and thousands of servers like it.
Across the catalogue