Move-Tool · Windows- MCP: Risk & Policy

WHAT IT DOES

What Move-Tool does on Windows-MCP

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

Moving the mouse cursor is an external interaction with the Windows UI environment that can trigger hover effects, tooltips, or UI state changes. While it doesn't click or modify data directly, it executes an OS-level action that affects the running system state. In the context of a Windows UI automation server alongside tools like Click-Tool and Powershell-Tool, cursor positioning is an active execution step.

From the tool's definition Move mouse cursor to specific coordinates without clicking. Useful for hovering over elements or positioning cursor before other actions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Move-Tool Rate-limited

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

FAQ

Questions about Move-Tool

What does the Move-Tool tool do? +

Move mouse cursor to specific coordinates without clicking. Useful for hovering over elements or positioning cursor before other actions. It is categorised as a Execute tool in the Windows-MCP 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-Tool? +

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

What risk level is Move-Tool? +

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

Can I rate-limit Move-Tool? +

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

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

Move-Tool is provided by the Windows- MCP server (stepbystep-1/winows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.