computer_move_mouse · LocalAnt MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why computer_move_mouse needs a policy

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

Recommended rule Ready

Verdict

computer_move_mouse Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "computer_move_mouse": {
      "limits": [
        {
          "counter": "computer_move_mouse_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocalAnt, so you can run agents against it safely.

FAQ

Questions about computer_move_mouse

What does the computer_move_mouse tool do? +

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.

How do I enforce a policy on computer_move_mouse? +

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.

What risk level is computer_move_mouse? +

computer_move_mouse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit computer_move_mouse? +

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.

How do I block computer_move_mouse completely? +

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.

What MCP server provides computer_move_mouse? +

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.