wait_for_window

THE RISK

High Risk

Why wait_for_window needs a policy

This tool executes an operation that waits for and monitors system state (window appearance), which is an external operation execution. While it doesn't directly modify or delete data like Write or Destructive tools, it actively triggers window detection logic based on provided arguments.

From the tool's definition Tool description states 'Wait for a window to appear' - this triggers external operations whose effects depend on arguments (process name or window title matching).

Documented attack patterns abuse exactly the kind of access wait_for_window gives an agent:

POLICY

How to control wait_for_window

PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_window:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait_for_window": {
      "limits": [
        {
          "counter": "wait_for_window_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wait_for_window 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.

Create a free account and register OODA Computer Control — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OODA Computer Control tools

Destructive batch_delete_files Delete multiple files in parallel. Destructive clear_old_logs Delete audit log entries older than specified days. Use dryRun=true to preview. Destructive clipboard_clear Clear the clipboard. Destructive crud_batch_delete Delete multiple records in parallel. Destructive crud_delete Delete a record Destructive delete_file Delete a file or directory. For multiple deletions, use batch_delete_files. Destructive reset_config Reset configuration to defaults. Optionally specify a section to reset only that section. Destructive kill_process Kill a process by PID or name.

All 99 OODA Computer Control tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in OODA Computer Control → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wait_for_window

What does the wait_for_window tool do? +

Wait for a window to appear. Matches process name or window title. It is categorised as a Execute tool in the OODA Computer Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait_for_window? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for wait_for_window: 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 OODA Computer Control. Nothing to install.

What risk level is wait_for_window? +

wait_for_window is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wait_for_window? +

Yes. Add a rate_limit block to the wait_for_window 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.

How do I block wait_for_window completely? +

Set action: deny in the PolicyLayer policy for wait_for_window. 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.

What MCP server provides wait_for_window? +

wait_for_window is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →