hover

Hover over the provided element

SERVERChrome DevTools MCP SOURCEanirbandz/chrome_mcp_devtool

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/anirbandz-chrome-mcp-devtool/hover.md

WHAT IT DOES

What hover does on Chrome DevTools MCP

AI agents invoke hover to trigger actions in Chrome DevTools 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.

RISK

Why hover is rated High

Hovering is a browser action that triggers external operations (e.g., mouseover events, tooltips, dynamic UI changes) in a live browser session. It falls under Execute as it causes side effects in the browser environment, though the blast radius is low since hover actions alone rarely cause irreversible harm.

From the tool's definition 'Hover over the provided element' — triggers a browser interaction (mouse hover) on a live Chrome browser via Chrome DevTools Protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hover, this is the rule to start with:

hover Rate-limited

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": {
    "hover": {
      "limits": [
        {
          "counter": "hover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome DevTools MCP, apply this rule, and every hover call is checked against it from then on.

FAQ

Questions about hover

What does the hover tool do? +

Hover over the provided element. It is categorised as a Execute tool in the Chrome DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hover? +

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

What risk level is hover? +

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

Can I rate-limit hover? +

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

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

hover is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome DevTools, and thousands of servers like it.

This server

All 26 Chrome DevTools tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →