double_click

What double_click does on Aos

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

A double_click action triggers UI interactions on Android or Windows desktop environments. This is an Execute-category action as it performs external operations (UI automation) whose effects depend on where the click is directed. The description is empty, so confidence is reduced, but sibling tools and server context strongly imply this performs a double-click action in an automation context.

From the tool's definition Tool name 'double_click' on a server providing Android device and Windows desktop automation capability (MaaFramework-based MCP server). Sibling tools include 'click', 'connect_adb_device', 'connect_window' confirming UI automation context.

The rule that runs double_click safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, 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:

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

Questions about double_click