Wait
Pauses execution for specified duration in seconds. Use when waiting for: applications to launch/load, UI animations to complete, page content to render, dialogs to appear, or between rapid actions. Helps ensure UI is ready before next interaction.
This record as markdown: /tools/13888285815-windows-mcp/wait.md
What Wait does on Windows-MCP
AI agents invoke Wait 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.
Why Wait is rated High
This is a control-flow tool that pauses execution. Although benign in isolation, it's an Execute category tool because it influences timing and sequencing of automated operations. It's low severity because waiting itself cannot directly damage systems, but it enables other sibling tools (Click, PowerShell, FileSystem, Process) to execute more reliably, making it part of the execution control pipeline.
From the tool's definition Tool pauses/delays execution for specified duration. While not directly performing system operations, it controls program flow and timing of subsequent actions in automation sequences.
Attacks that exploit this kind of access
The rule that runs Wait safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Windows-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Wait, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Windows-MCP, apply this rule, and every Wait call is checked against it from then on.
Questions about Wait
Pauses execution for specified duration in seconds. Use when waiting for: applications to launch/load, UI animations to complete, page content to render, dialogs to appear, or between rapid actions. Helps ensure UI is ready before next interaction. 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: 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 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 Windows MCP server (13888285815/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Windows, and thousands of servers like it.
Across the catalogue