element_hover
Hover over an element (triggers hover/mouseover state).
This record as markdown: /tools/mcp-anything/element-hover.md
What element_hover does on Mcp Anything
AI agents invoke element_hover to trigger actions in Mcp Anything. 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 element_hover is rated High
This tool triggers a browser/UI interaction (mouseover event) on an element, which is an external operation that executes an action in a UI context. Hovering can trigger side effects like dropdown menus appearing, tooltips, or JavaScript event handlers firing. This falls under Execute as it performs a browser action whose effects depend on which element is targeted.
From the tool's definition Hover over an element (triggers hover/mouseover state)
Attacks that exploit this kind of access
The rule that runs element_hover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For element_hover, this is the rule to start with:
element_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every element_hover call is checked against it from then on.
Questions about element_hover
Hover over an element (triggers hover/mouseover state). It is categorised as a Execute tool in the Mcp Anything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for element_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 Mcp Anything. Nothing to install.
element_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 element_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 element_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.
element_hover is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
Across the catalogue