move_mouse_to · Simple MCP: Risk & Policy

WHAT IT DOES

What move_mouse_to does on Simple MCP

AI agents invoke move_mouse_to to trigger actions in Simple 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_mouse_to needs a policy

This tool performs a physical mouse movement action on the system, which is an external operation affecting the UI state. It's not just reading data, and while reversible in principle, it triggers real system-level UI interaction that could be part of a chain of automated actions. It falls under Execute as it triggers an external operation (cursor movement) whose effect depends on the coordinates argument.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_mouse_to Rate-limited

move_mouse_to 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_to": {
      "limits": [
        {
          "counter": "move_mouse_to_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 Simple MCP, so you can run agents against it safely.

FAQ

Questions about move_mouse_to

What does the move_mouse_to tool do? +

Move the mouse cursor to the specified screen coordinates. It is categorised as a Execute tool in the Simple 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_mouse_to? +

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

What risk level is move_mouse_to? +

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

Can I rate-limit move_mouse_to? +

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

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

move_mouse_to is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.