computer_drag · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What computer_drag does on LocalAnt

AI agents invoke computer_drag to trigger actions in LocalAnt. 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 computer_drag needs a policy

This tool performs a physical UI interaction (drag action) on the user's PC via browser/desktop automation. It triggers an external operation whose effect depends on arguments (coordinates), placing it in the Execute category. The 'risk 3' approval requirement and the broad potential for misuse (dragging files, UI elements, triggering actions) give it high severity.

From the tool's definition Drag from x1,y1 to x2,y2 (screenshot coordinates). Requires approval (risk 3).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

computer_drag Rate-limited

computer_drag 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": {
    "computer_drag": {
      "limits": [
        {
          "counter": "computer_drag_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about computer_drag

What does the computer_drag tool do? +

Drag from x1,y1 to x2,y2 (screenshot coordinates). Requires approval (risk 3). It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on computer_drag? +

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

What risk level is computer_drag? +

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

Can I rate-limit computer_drag? +

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

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

computer_drag is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.