browser_hover

Hover the mouse over an element (reveals tooltips + hover menus). ref is a CSS selector.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-hover.md

WHAT IT DOES

What browser_hover does on Dialogbrain

AI agents invoke browser_hover to trigger actions in Dialogbrain. 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.

Parameter	Type	Required	Description
`ref`	string	Yes
`page_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why browser_hover is rated High

This tool performs a browser action (mouse hover) that triggers UI interactions such as revealing tooltips and hover menus. It is an Execute-category tool as it triggers external browser operations whose effects depend on the provided CSS selector argument. While hovering itself is generally non-destructive, it can trigger dynamic UI behaviors and is part of a broader browser automation capability.

From the tool's definition Hover the mouse over an element (reveals tooltips + hover menus). `ref` is a CSS selector.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_hover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_hover": {
      "limits": [
        {
          "counter": "browser_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 Dialogbrain, apply this rule, and every browser_hover call is checked against it from then on.

FAQ

Questions about browser_hover

What does the browser_hover tool do? +

Hover the mouse over an element (reveals tooltips + hover menus). ref is a CSS selector. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browser_hover accept? +

browser_hover accepts 2 parameters: ref, page_id. Required: ref, page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_hover? +

Register the Dialogbrain 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 Dialogbrain. Nothing to install.

What risk level is browser_hover? +

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

Can I rate-limit browser_hover? +

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.

How do I block browser_hover completely? +

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.

What MCP server provides browser_hover? +

browser_hover is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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