ax_click · MacWright MCP: Risk & Policy

WHAT IT DOES

What ax_click does on MacWright

AI agents invoke ax_click to trigger actions in MacWright. 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 ax_click needs a policy

This tool performs a UI click action on native macOS elements, which triggers external operations depending on what element is clicked. Clicking UI elements can open files, submit forms, trigger destructive actions, or execute arbitrary application functions, making it an Execute-category tool with high severity due to broad potential impact.

From the tool's definition Find a native macOS UI element by its label text and click its center

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ax_click Rate-limited

ax_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": {
    "ax_click": {
      "limits": [
        {
          "counter": "ax_click_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 MacWright, so you can run agents against it safely.

FAQ

Questions about ax_click

What does the ax_click tool do? +

Find a native macOS UI element by its label text and click its center. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ax_click? +

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

What risk level is ax_click? +

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

Can I rate-limit ax_click? +

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

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

ax_click is provided by the MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.