computer_left_click · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What computer_left_click does on LocalAnt

AI agents invoke computer_left_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_left_click needs a policy

Clicking UI elements is an active browser/desktop automation action that triggers external operations depending on where the click lands. The effect is entirely argument-dependent — a click can submit forms, launch applications, delete files via GUI, etc. — making it Execute.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

computer_left_click Rate-limited

computer_left_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_left_click": {
      "limits": [
        {
          "counter": "computer_left_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_left_click

What does the computer_left_click tool do? +

Left-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_left_click? +

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

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

Can I rate-limit computer_left_click? +

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

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

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

// THE FULL RECORD

computer_left_click is one line of LocalAnt's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →