hover · Chrome Profile MCP Server MCP: Risk & Policy

WHAT IT DOES

What hover does on Chrome Profile MCP Server

AI agents invoke hover to trigger actions in Chrome Profile 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 hover needs a policy

Hovering over elements in a real browser session can trigger JavaScript events (mouseover, mouseenter), reveal dropdown menus, initiate lazy-loads, or cause other dynamic UI changes. This is an active browser operation with potential side effects beyond mere reading, making it Execute. Severity is medium because misuse could trigger unintended UI interactions but is generally reversible and limited in blast radius.

From the tool's definition 'Hover over an element' — triggers browser interaction via Chrome DevTools Protocol, causing external side effects such as revealing menus, tooltips, or triggering hover-based UI events on a live Chrome instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome Profile MCP Server, so you can run agents against it safely.

FAQ

Questions about hover

What does the hover tool do? +

Hover over an element. It is categorised as a Execute tool in the Chrome Profile 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 hover? +

Register the Chrome Profile MCP Server 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 Profile MCP Server. 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 Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.