High Risk →

wait

Pause execution for a specified duration. Useful for waiting between UI operations.

Part of the Mac Use server.

wait can trigger actions in Mac Use, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MAC USE →

Free to start. No card required.

AI agents invoke wait to trigger processes or run actions in Mac Use. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

wait can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait": {
      "limits": [
        {
          "counter": "wait_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mac Use policy for all 17 tools.

Get this rule live on your own Mac Use server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MAC USE →

View all 17 tools →

These attack patterns abuse exactly the kind of access wait gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so wait only ever does what you allow.

SECURE MAC USE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the wait tool do? +

Pause execution for a specified duration. Useful for waiting between UI operations.. It is categorised as a Execute tool in the Mac Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait? +

Register the Mac Use 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 Mac Use. Nothing to install.

What risk level is wait? +

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

Can I rate-limit wait? +

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.

How do I block wait completely? +

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.

What MCP server provides wait? +

wait is provided by the Mac Use MCP server (mac-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mac Use tool call.

Deterministic rules across all 17 Mac Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.