safari_wait_for
Polls the current Safari tab until a CSS selector appears (or its text matches, if text_match is provided). Useful after safari_click to wait for the next page or a modal to render.
This record as markdown: /tools/com-local-mcp-local-mcp/safari-wait-for.md
What safari_wait_for does on Local
AI agents invoke safari_wait_for 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 |
|---|---|---|---|
selector | string | Yes | CSS selector to wait for |
text_match | string | — | Optional substring that must appear inside the matched element |
timeout_ms | integer | — | Max time to wait (default 10000 = 10s, max 30000) |
Parameters from the server's own tool schema.
Why safari_wait_for is rated High
This tool executes a polling operation on a live Safari browser instance, which is an active external operation whose effects depend on the runtime state of the browser. While non-destructive, it orchestrates browser state transitions and can be chained with other browser actions (click, navigate, fill_form) to achieve consequential side effects.
From the tool's definition Tool name 'safari_wait_for' and description 'Polls the current Safari tab until a CSS selector appears' indicates active browser polling/monitoring.
Attacks that exploit this kind of access
The rule that runs safari_wait_for 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_wait_for, this is the rule to start with:
safari_wait_for 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_wait_for call is checked against it from then on.
Questions about safari_wait_for
Polls the current Safari tab until a CSS selector appears (or its text matches, if text_match is provided). Useful after safari_click to wait for the next page or a modal to render. 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_wait_for accepts 3 parameters: selector, text_match, timeout_ms. 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_wait_for: 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_wait_for 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_wait_for 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_wait_for. 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_wait_for 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