wait · Computer Use MCP Server MCP: Risk & Policy

WHAT IT DOES

What wait does on Computer Use MCP Server

AI agents invoke wait to trigger actions in Computer Use 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.

WHY IT NEEDS A POLICY

Why wait needs a policy

While this tool has minimal direct impact, it is an Execute category tool because it triggers an external operation (a timed delay) that the AI agent controls via arguments (duration in seconds). It does not read, write, or destroy data. In the context of a desktop automation MCP server, it would be used to sequence or synchronize other automation actions.

From the tool's definition Tool description states 'Wait for a specified duration in seconds.' This is a timing/delay operation that affects control flow execution on the desktop automation system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait": {
      "limits": [
        {
          "counter": "wait_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 Computer Use MCP Server, so you can run agents against it safely.

FAQ

Questions about wait

What does the wait tool do? +

Wait for a specified duration in seconds. It is categorised as a Execute tool in the Computer Use MCP Server 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 Computer Use 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 Computer Use MCP Server. 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 Computer Use MCP Server MCP server (syedazharmbnr1/computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

wait is one line of Computer Use MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →