Hover action, Move the mouse to the element. Parameters: locate (object) - The element to be hovered
AI agents invoke Hover to trigger actions in Web Bridge. 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 |
|---|---|---|---|
locate | object | Yes | The element to be hovered |
web.url | string | — | URL to open in new tab (omit to use current page) |
web.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
web.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
web.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
web.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
Hovering moves the mouse cursor to a UI element in a browser automation context. This is an external browser action whose effects depend on the target element (e.g., triggering tooltips, dropdown menus, or JavaScript hover events). It doesn't read data, write/modify persistent data, or destroy anything, but it does execute a browser interaction, making Execute the most appropriate category.
From the tool's definition 'Hover action, Move the mouse to the element' — triggers a browser mouse-move interaction on a target element
Risk signalsAccepts URL/endpoint input (web.url) · High parameter count (11 properties)
Attacks that exploit this kind of access
Hover action, Move the mouse to the element. Parameters: locate (object) - The element to be hovered. It is categorised as a Execute tool in the Web Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Hover accepts 6 parameters: locate, web.url, web.aiActContext, web.waitAfterAction, web.replanningCycleLimit, web.screenshotShrinkFactor. Required: locate. The full parameter table on this page comes from the server's own tool schema.
Register the Web Bridge 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 Web Bridge. Nothing to install.
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 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 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.
Hover is provided by the Web Bridge MCP server (@midscene/web-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →