safari_click
Clicks the first element matching a CSS selector in the current Safari tab. Returns the tag name and visible text of the clicked element so you can confirm the right thing was hit. Pass wait_for_navigation: true to wait up to 3 seconds for the page to load after the click (useful when clicking li...
This record as markdown: /tools/com-local-mcp-local-mcp/safari-click.md
What safari_click does on Local
AI agents invoke safari_click to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
nth | integer | — | Which match to click if there are several (0-based, default 0) |
selector | string | Yes | CSS selector (e.g. 'button.primary', '#save', '[data-testid=login]') |
wait_for_navigation | boolean | — | Wait up to 3s for page load after click (default false) |
Parameters from the server's own tool schema.
Why safari_click is rated High
Clicking UI elements in a browser is an Execute-class action — it triggers external operations (navigation, form submissions, button actions) whose effects depend entirely on what element is targeted. Misuse could trigger arbitrary web actions such as purchases, deletions, or account changes.
From the tool's definition Clicks the first element matching a CSS selector in the current Safari tab
Attacks that exploit this kind of access
The rule that runs safari_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For safari_click, this is the rule to start with:
safari_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every safari_click call is checked against it from then on.
Questions about safari_click
Clicks the first element matching a CSS selector in the current Safari tab. Returns the tag name and visible text of the clicked element so you can confirm the right thing was hit. Pass wait_for_navigation: true to wait up to 3 seconds for the page to load after the click (useful when clicking links or buttons that trigger navigation). It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
safari_click accepts 3 parameters: nth, selector, wait_for_navigation. Required: selector. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for safari_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 Local. Nothing to install.
safari_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the safari_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.
Set action: deny in the PolicyLayer policy for safari_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.
safari_click is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue