mouse_move · Windows MCP Server MCP: Risk & Policy

WHAT IT DOES

What mouse_move does on Windows MCP Server

AI agents invoke mouse_move to trigger actions in Windows MCP Server. 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 mouse_move needs a policy

Moving the mouse cursor is an external system-level action that manipulates the Windows UI environment. While moving alone has minimal direct impact, it is an Execute-class action as it controls system input and can be chained with other tools (like click) to trigger unintended UI interactions. Severity is low because mouse movement alone causes no direct data modification or deletion.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mouse_move Rate-limited

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

FAQ

Questions about mouse_move

What does the mouse_move tool do? +

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

How do I enforce a policy on mouse_move? +

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

What risk level is mouse_move? +

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

Can I rate-limit mouse_move? +

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

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

mouse_move is provided by the Windows MCP Server MCP server (romeo2badboy-rgb/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.