computer_move_mouse
Move the mouse cursor to x,y (screenshot coordinates) without clicking.
This record as markdown: /tools/yuga-hashimoto-localant/computer-move-mouse.md
What computer_move_mouse does on LocalAnt
AI agents invoke computer_move_mouse to trigger actions in LocalAnt. 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 computer_move_mouse is rated High
Moving the mouse cursor is a browser/desktop automation action that triggers external operations on the host PC. While it doesn't click or directly modify data, it is a physical input action on the user's machine that can position the cursor for follow-up actions, making it an Execute-category tool.
From the tool's definition Move the mouse cursor to x,y (screenshot coordinates) without clicking
Attacks that exploit this kind of access
The rule that runs computer_move_mouse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For computer_move_mouse, this is the rule to start with:
computer_move_mouse 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 LocalAnt, apply this rule, and every computer_move_mouse call is checked against it from then on.
Questions about computer_move_mouse
Move the mouse cursor to x,y (screenshot coordinates) without clicking. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LocalAnt MCP server in PolicyLayer and add a rule for computer_move_mouse: 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 LocalAnt. Nothing to install.
computer_move_mouse 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 computer_move_mouse 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 computer_move_mouse. 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.
computer_move_mouse is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue