Hover over a DOM element in Safari by CSS selector. Moves the mouse over the element without clicking — useful for triggering hover states, showing dropdown menus, revealing tooltips, or testing CSS :hover effects.
AI agents invoke hover_element to trigger actions in MacWright. 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.
Although hovering does not click or modify data, it triggers external UI operations (hover states, dropdown menus, tooltips) via browser automation in Safari. This constitutes driving an external application's behavior, which falls under Execute.
From the tool's definition Moves the mouse over the element without clicking — useful for triggering hover states, showing dropdown menus, revealing tooltips
Attacks that exploit this kind of access
Hover over a DOM element in Safari by CSS selector. Moves the mouse over the element without clicking — useful for triggering hover states, showing dropdown menus, revealing tooltips, or testing CSS :hover effects. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MacWright MCP server in PolicyLayer and add a rule for hover_element: 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 MacWright. Nothing to install.
hover_element 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_element 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_element. 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_element is provided by the MacWright MCP server (ruchit-p/macwright). 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 →