computer_left_click

Left-click at x,y (screenshot coordinates). Requires approval (risk 3).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/computer-left-click.md

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.

RISK

Why computer_left_click is rated High

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

The rule that runs computer_left_click safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For computer_left_click, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every computer_left_click call is checked against it from then on.

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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →