computer_double_click · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What computer_double_click does on LocalAnt

AI agents invoke computer_double_click 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_double_click needs a policy

This tool performs a UI interaction (double-click) at arbitrary screen coordinates, triggering whatever action is bound to that location on the user's PC. An AI agent could double-click executables, buttons, or links with unpredictable and potentially severe side effects depending on what is on screen.

From the tool's definition Double-click at x,y (screenshot coordinates). Requires approval (risk 3).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

computer_double_click Rate-limited

computer_double_click 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_double_click": {
      "limits": [
        {
          "counter": "computer_double_click_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_double_click

What does the computer_double_click tool do? +

Double-click at x,y (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_double_click? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for computer_double_click: 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_double_click? +

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

Can I rate-limit computer_double_click? +

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

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

computer_double_click 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.