Hover over an element to trigger mouseover events and reveal hidden UI (e.g., dropdown menus, tooltips)
AI agents invoke hover to trigger actions in Webclaw. 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.
The hover tool executes browser events and triggers state changes in the DOM/UI. While not destructive or financial, it is an action that causes the browser to perform operations that could expose functionality for further interaction. This fits Execute rather than Read because it actively triggers events and modifies UI state, not merely querying existing data.
From the tool's definition Tool description states it "trigger[s] mouseover events" and is used to "reveal hidden UI (e.g., dropdown menus, tooltips)".
Documented attack patterns abuse exactly the kind of access hover gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for hover:
{
"version": "1",
"default": "deny",
"tools": {
"hover": {
"limits": [
{
"counter": "hover_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Hover over an element to trigger mouseover events and reveal hidden UI (e.g., dropdown menus, tooltips). It is categorised as a Execute tool in the Webclaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webclaw 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 Webclaw. 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 Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webclaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Webclaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.