desktop_mouse_move · MCP Desktop Tools MCP: Risk & Policy

WHAT IT DOES

What desktop_mouse_move does on MCP Desktop Tools

AI agents invoke desktop_mouse_move to trigger actions in MCP Desktop Tools. 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 desktop_mouse_move needs a policy

Moving the mouse cursor is a desktop automation action that triggers an external operation on the system. While moving the mouse alone has limited direct impact, it is part of a broader automation capability and can interact with UI elements, making it an Execute-category tool. In the context of this server's automation suite, misuse could enable unintended UI interactions.

From the tool's definition Move the mouse cursor to screen coordinates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

desktop_mouse_move Rate-limited

desktop_mouse_move 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": {
    "desktop_mouse_move": {
      "limits": [
        {
          "counter": "desktop_mouse_move_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 MCP Desktop Tools, so you can run agents against it safely.

FAQ

Questions about desktop_mouse_move

What does the desktop_mouse_move tool do? +

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

How do I enforce a policy on desktop_mouse_move? +

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

What risk level is desktop_mouse_move? +

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

Can I rate-limit desktop_mouse_move? +

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

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

desktop_mouse_move is provided by the MCP Desktop Tools MCP server (k1ta141k/mcp-desktop-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.