click_ui_element · Mac MCP: Risk & Policy

WHAT IT DOES

What click_ui_element does on Mac

AI agents invoke click_ui_element to trigger actions in Mac. 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 IT NEEDS A POLICY

Why click_ui_element needs a policy

Clicking a UI element triggers an action in the macOS UI — it could activate buttons, confirm dialogs, submit forms, or trigger any arbitrary application behavior. The effect depends entirely on which element is clicked, making this an Execute-category tool with high severity since an AI agent could misuse it to confirm destructive or financial operations through the UI.

From the tool's definition Clicks a UI element by path

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_ui_element Rate-limited

click_ui_element 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": {
    "click_ui_element": {
      "limits": [
        {
          "counter": "click_ui_element_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mac, so you can run agents against it safely.

FAQ

Questions about click_ui_element

What does the click_ui_element tool do? +

Clicks a UI element by path (e.g.,. It is categorised as a Execute tool in the Mac MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on click_ui_element? +

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

What risk level is click_ui_element? +

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

Can I rate-limit click_ui_element? +

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

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

click_ui_element is provided by the Mac MCP server (laststance/mac-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.