click_element · MacWright MCP: Risk & Policy

WHAT IT DOES

What click_element does on MacWright

AI agents invoke click_element 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 click_element needs a policy

This tool performs browser automation by clicking DOM elements in Safari, triggering arbitrary UI interactions on web pages. Clicking can submit forms, initiate purchases, change settings, or trigger any web action — making it an Execute-category tool with high severity due to the broad and potentially irreversible effects of automated web clicks.

From the tool's definition Click a DOM element in Safari by CSS selector... web automation pattern... Use jsClick for SPAs (GitHub, React apps) where native clicks don

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_element Rate-limited

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

FAQ

Questions about click_element

What does the click_element tool do? +

Click a DOM element in Safari by CSS selector. Combines find_element + click in one step — the most common web automation pattern. Use this instead of find_element followed by click(). Supports auto-waiting with timeout param. Use jsClick for SPAs (GitHub, React apps) where native clicks don. 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 click_element? +

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

What risk level is click_element? +

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

Can I rate-limit click_element? +

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

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

click_element 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.