wavexis_mouse_move_xy
Move the mouse to absolute pixel coordinates.
This record as markdown: /tools/wavexis-mcp/wavexis-mouse-move-xy.md
What wavexis_mouse_move_xy does on Wavexis
AI agents invoke wavexis_mouse_move_xy to trigger actions in Wavexis. 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 wavexis_mouse_move_xy is rated High
This tool performs a browser automation action (moving the mouse cursor to specific coordinates), which is an external operation that triggers UI interactions. It falls under Execute as it drives browser/UI behavior rather than simply reading data or writing structured content. Misuse could be part of a chain of actions to click unintended UI elements, but on its own the blast radius is moderate.
From the tool's definition Move the mouse to absolute pixel coordinates
Attacks that exploit this kind of access
The rule that runs wavexis_mouse_move_xy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_mouse_move_xy, this is the rule to start with:
wavexis_mouse_move_xy 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 Wavexis, apply this rule, and every wavexis_mouse_move_xy call is checked against it from then on.
Questions about wavexis_mouse_move_xy
Move the mouse to absolute pixel coordinates. It is categorised as a Execute tool in the Wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_mouse_move_xy: 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 Wavexis. Nothing to install.
wavexis_mouse_move_xy 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 wavexis_mouse_move_xy 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 wavexis_mouse_move_xy. 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.
wavexis_mouse_move_xy is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
Across the catalogue