Sleep for ms milliseconds (useful to wait for page loads/animations).
AI agents invoke wait to trigger actions in Hermes 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.
This tool triggers external operations (pausing/timing control) whose effects depend on the argument (milliseconds duration). While it has minimal blast radius compared to other browser automation tools on this server, it is fundamentally an Execute action as it controls program flow and timing during automated browser operations.
From the tool's definition Tool performs a sleep/wait operation that pauses execution for a specified duration (ms milliseconds). Within the context of browser automation ('drives a real Chrome browser'), this is an execution action that controls the timing of automated operations.
Attacks that exploit this kind of access
Sleep for ms milliseconds (useful to wait for page loads/animations). It is categorised as a Execute tool in the Hermes Computer Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hermes 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 Hermes 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 Hermes Computer Use MCP server (noah3521/hermes-computer-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →