drag_mouse · macOS Control MCP Server MCP: Risk & Policy

WHAT IT DOES

What drag_mouse does on macOS Control MCP Server

AI agents invoke drag_mouse to trigger actions in macOS Control 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 drag_mouse needs a policy

The drag_mouse tool performs a mouse drag action, which is a desktop automation operation. On a macOS automation server using PyAutoGUI, dragging can trigger arbitrary UI interactions — moving files, rearranging UI elements, interacting with applications — making it an Execute-level action. The description is empty, lowering confidence, but context from the server and sibling tools strongly implies GUI automation.

From the tool's definition Tool name 'drag_mouse' on a server that 'Enables full desktop automation on macOS through natural language, including mouse control' using PyAutoGUI.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drag_mouse Rate-limited

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

FAQ

Questions about drag_mouse

What does the drag_mouse tool do? +

drag_mouse. It is categorised as a Execute tool in the macOS Control 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 drag_mouse? +

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

What risk level is drag_mouse? +

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

Can I rate-limit drag_mouse? +

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

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

drag_mouse is provided by the macOS Control MCP Server MCP server (lodimup/macos-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.