// MCP TOOL REFERENCE

orgo_click

Click at pixel (x, y) coordinates on the VM display. Coordinates are in 1280x720 model space. Use only when GUI interaction is genuinely required — for anything scriptable, prefer

ServerOrgo MCP Server
CategoryExecute

How to control orgo_click ↓

WHAT IT DOES

What orgo_click does on Orgo MCP Server

AI agents invoke orgo_click to trigger actions in Orgo 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.

THE RISK

High Risk

Why orgo_click needs a policy

This tool performs a browser/GUI action (mouse click) on a virtual machine display. It triggers external operations whose effects depend on arguments — clicking different coordinates could submit forms, open applications, trigger destructive UI actions, etc. The effects are context-dependent and not directly reversible, placing it firmly in Execute.

From the tool's definition Click at pixel (x, y) coordinates on the VM display

Documented attack patterns abuse exactly the kind of access orgo_click gives an agent:

POLICY

How to control orgo_click

PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_click:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "orgo_click": {
      "limits": [
        {
          "counter": "orgo_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Orgo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Orgo MCP Server tools

Destructive orgo_delete_computer Permanently delete a computer and all its data. Cannot be undone. Use only when explicitly Destructive orgo_delete_workspace Permanently delete a workspace and all of its computers. Cannot be undone. Use only when e Destructive orgo_restart_computer Restart a computer. Useful for recovering from unresponsive states. Use when commands hang Execute orgo_bash Execute a bash command on the VM. Uses WebSocket terminal (preferred) with REST API fallba Execute orgo_ensure_running Ensure a computer is running. Resumes suspended VMs automatically. Idempotent. Use before Execute orgo_exec Execute Python code on the computer. Returns output or error details. Use for computation, Execute orgo_wait Pause execution on the VM for a fixed duration. Useful for sequencing actions between scre Execute orgo_drag Drag from (start_x, start_y) to (end_x, end_y). Coordinates in 1280x720 model space. Use f

All 28 Orgo MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Orgo MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about orgo_click

What does the orgo_click tool do? +

Click at pixel (x, y) coordinates on the VM display. Coordinates are in 1280x720 model space. Use only when GUI interaction is genuinely required — for anything scriptable, prefer. It is categorised as a Execute tool in the Orgo 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 orgo_click? +

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

What risk level is orgo_click? +

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

Can I rate-limit orgo_click? +

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

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

orgo_click is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orgo MCP Server tool call.

Start from Orgo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.