Wait for a specified number of milliseconds. Args: milliseconds: Number of milliseconds to wait Returns: Success message after waiting
AI agents call wait_milliseconds as a supporting operation in Computer Control MCP workflows.
This tool only pauses execution for a given duration. It does not read, write, execute, destroy, or move money. It is a timing/synchronization utility with minimal blast radius; misuse at worst wastes time.
From the tool's definition 'Wait for a specified number of milliseconds' — simply introduces a time delay with no side effects on data, files, or external systems.
Documented attack patterns abuse exactly the kind of access wait_milliseconds gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Computer Control MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_milliseconds:
{
"version": "1",
"default": "deny",
"tools": {
"wait_milliseconds": {
"limits": [
{
"counter": "wait_milliseconds_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}wait_milliseconds gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Wait for a specified number of milliseconds. Args: milliseconds: Number of milliseconds to wait Returns: Success message after waiting. It is categorised as a Other tool in the Computer Control MCP MCP Server, which means it performs auxiliary operations.
Register the Computer Control MCP server in PolicyLayer and add a rule for wait_milliseconds: 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 Control MCP. Nothing to install.
wait_milliseconds is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wait_milliseconds 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_milliseconds. 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_milliseconds is provided by the Computer Control MCP server (ab498/computer-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Computer Control MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Computer Control MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.