move_mouse · Macinput MCP: Risk & Policy

WHAT IT DOES

What move_mouse does on Macinput

AI agents invoke move_mouse to trigger actions in Macinput. 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 move_mouse needs a policy

Moving the mouse is an external operation that affects the desktop environment. While moving alone may seem benign, in the context of a GUI automation server, it is a prerequisite for UI interactions and constitutes an Execute-level action. It can be used to aim at UI elements before clicks, enabling agent-driven desktop workflows with moderate blast radius.

From the tool's definition Move the cursor to absolute screen coordinates — triggers an external desktop GUI operation (mouse movement) that can position the cursor to enable subsequent clicks or interactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_mouse Rate-limited

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": {
    "move_mouse": {
      "limits": [
        {
          "counter": "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 Macinput, so you can run agents against it safely.

FAQ

Questions about move_mouse

What does the move_mouse tool do? +

Move the cursor to absolute screen coordinates. It is categorised as a Execute tool in the Macinput MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on move_mouse? +

Register the Macinput MCP server in PolicyLayer and add a rule for 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 Macinput. Nothing to install.

What risk level is move_mouse? +

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

Can I rate-limit move_mouse? +

Yes. Add a rate_limit block to the 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 move_mouse completely? +

Set action: deny in the PolicyLayer policy for 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 move_mouse? +

move_mouse is provided by the Macinput MCP server (sigma711/macinput). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.