AI agents invoke wait to trigger actions in Computer Use. 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 waiting itself is benign, this tool triggers execution of external operations (system timer/sleep functions) whose effects depend on the argument provided (duration in seconds). It is part of a Computer Use server alongside bash execution and GUI automation tools, indicating it serves as a control-flow primitive for orchestrating other operations.
From the tool's definition Tool is named 'wait' and description states it 'Wait[s] for the specified number of seconds.' This is a blocking operation that triggers execution of a time-delay function.
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 Computer Use, 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.
Wait for the specified number of seconds. It is categorised as a Execute tool in the Computer Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer 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 Computer Use. 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 Computer Use MCP server (spencerkinney/computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Computer Use, 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.
15 Computer Use tools catalogued and risk-classified — across an index of 43,000+ MCP servers.