Pause execution for specified duration in seconds. Useful for waiting for applications to load, animations to complete, or adding delays between actions.
AI agents invoke Wait-Tool to trigger actions in Windows-MCP. 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.
Wait-Tool is classified as Execute rather than Read because it actively controls the execution state and timing of automated actions, not merely querying data. It has minimal severity (low) because the tool itself cannot cause harm—it simply introduces delays. However, it is strictly more severe than Read since it modifies operational behavior.
From the tool's definition The tool triggers execution of a pause/delay operation that affects the timing and sequencing of automated operations.
Attacks that exploit this kind of access
Pause execution for specified duration in seconds. Useful for waiting for applications to load, animations to complete, or adding delays between actions. It is categorised as a Execute tool in the Windows-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Windows- MCP server in PolicyLayer and add a rule for Wait-Tool: 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 Windows-MCP. Nothing to install.
Wait-Tool 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-Tool 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-Tool. 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-Tool is provided by the Windows- MCP server (zhouke2020/cursortouch-windows-mcp). 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 →