move_mouse · Desk MCP: Risk & Policy

WHAT IT DOES

What move_mouse does on Desk

AI agents invoke move_mouse to trigger actions in Desk. 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 interacts with the desktop environment via xdotool. While it doesn't click, it still triggers cursor movement which can have side effects (e.g., triggering hover states, tooltips, or focus changes). It's an input simulation action rather than a pure read, write, or destructive operation.

From the tool's definition Move mouse to coordinates without clicking

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 Desk, so you can run agents against it safely.

FAQ

Questions about move_mouse

What does the move_mouse tool do? +

Move mouse to coordinates without clicking. It is categorised as a Execute tool in the Desk 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 Desk 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 Desk. 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 Desk MCP server (kpihx/desk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.