Pause execution for a specified duration in milliseconds to allow time for UI updates, animations, network requests, or application responses. Critical for reliable automation timing - prevents race conditions and ensures UI elements have time to load or respond. Use between actions when applicat...
AI agents invoke wait to trigger actions in macOS Simulator MCP Server. 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.
While the wait function itself is not destructive or immediately dangerous, it is part of an Execute category workflow. The tool directly controls automation timing for a system that can click buttons, type keyboard input, and control mouse movements on macOS applications. Misuse could be combined with other sibling tools (click, keyboard input) to automate harmful sequences.
From the tool's definition Tool description states it "Pause[s] execution for a specified duration in milliseconds" and is used "between actions when applications need time to process." It controls timing of automated workflows that interact with macOS applications via mouse and…
Documented attack patterns abuse exactly the kind of access wait gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wait:
{
"version": "1",
"default": "deny",
"tools": {
"wait": {
"limits": [
{
"counter": "wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}wait 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.
Free to start. No card required.
Pause execution for a specified duration in milliseconds to allow time for UI updates, animations, network requests, or application responses. Critical for reliable automation timing - prevents race conditions and ensures UI elements have time to load or respond. Use between actions when applications need time to process (e.g., after clicking a button that triggers loading, before taking a screenshot of updated content, or while waiting for dialogs to appear). Typical values: 500-1000ms for UI updates, 2000-5000ms for network operations. Essential tool for stable, reliable automation workflows. It is categorised as a Execute tool in the macOS Simulator MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the macOS Simulator MCP Server MCP server in PolicyLayer and add a rule for wait: 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 macOS Simulator MCP Server. Nothing to install.
wait 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 wait 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 wait. 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.
wait is provided by the macOS Simulator MCP Server MCP server (ohqay/mac-commander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from macOS Simulator MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 macOS Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.