double_click

Double-click inside the current controlled window using screenshot-relative coordinates. Returns a fresh screenshot.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/double-click.md

WHAT IT DOES

What double_click does on CoWork OS

AI agents invoke double_click to trigger actions in CoWork OS. 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 double_click is rated High

This tool performs a UI interaction (double-click) on a controlled window, triggering actions that depend on what is under the cursor — could open files, execute programs, confirm dialogs, or trigger arbitrary application behavior. Effects are context-dependent and potentially wide-ranging, making it Execute with high severity.

From the tool's definition Double-click inside the current controlled window using screenshot-relative coordinates

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs double_click safely

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

double_click Rate-limited

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": {
    "double_click": {
      "limits": [
        {
          "counter": "double_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 CoWork OS, apply this rule, and every double_click call is checked against it from then on.

FAQ

Questions about double_click

What does the double_click tool do? +

Double-click inside the current controlled window using screenshot-relative coordinates. Returns a fresh screenshot. It is categorised as a Execute tool in the CoWork OS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on double_click? +

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

What risk level is double_click? +

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

Can I rate-limit double_click? +

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

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

double_click is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS 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 →