Hover over the provided element
AI agents invoke hover to trigger actions in Opera 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.
Hovering over an element is a browser action that can trigger side effects such as tooltips, dropdown menus, JavaScript event handlers (mouseover, mouseenter), or dynamic content loading. It is not a pure read operation since it actively interacts with the browser. Severity is low because hover actions rarely cause irreversible or high-impact changes, but they can still trigger unintended UI interactions.
From the tool's definition 'Hover over the provided element' — triggers a browser interaction/action on a DOM element
Attacks that exploit this kind of access
Hover over the provided element. It is categorised as a Execute tool in the Opera DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Opera 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 Opera DevTools MCP. 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 Opera DevTools MCP server (operasoftware/opera-devtools-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 →