click_element

What click_element does on Aos

AI agents invoke click_element 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 click_element is rated High

Given the server's purpose (sandboxed computer-use MCP driving a real browser and desktop apps) and sibling tools that are all browser/desktop interaction primitives, 'click_element' almost certainly triggers a UI click action in a live environment. Clicking elements can trigger arbitrary operations (form submissions, downloads, navigation, deletions), making this an Execute-level tool.

From the tool's definition Tool name 'click_element' on a server described as 'drive a real browser + desktop apps in a nested X11 window'; sibling tools include 'click', 'double_click', 'drag' confirming UI automation context. Description is empty.

The rule that runs click_element 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 click_element, this is the rule to start with:

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

Questions about click_element