os_wait · OScribe MCP: Risk & Policy

WHAT IT DOES

What os_wait does on OScribe

AI agents invoke os_wait to trigger actions in OScribe. 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 IT NEEDS A POLICY

Why os_wait needs a policy

While os_wait appears passive (waiting), it is a fundamental control primitive in an Execute context. Within OScribe's automation framework, it orchestrates timing of subsequent desktop control actions. A misused delay could cause an agent to wait indefinitely, skip critical actions, or trigger unintended sequences of commands on user systems.

From the tool's definition Tool waits for a specified duration during UI automation. Described as part of vision-based desktop automation that 'controls any application' and 'enables UI automation through natural language commands.' The os_wait function itself delays execution, which…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

os_wait Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OScribe, so you can run agents against it safely.

FAQ

Questions about os_wait

What does the os_wait tool do? +

Wait for a specified duration (useful for waiting for UI to load). It is categorised as a Execute tool in the OScribe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on os_wait? +

Register the OScribe MCP server in PolicyLayer and add a rule for os_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 OScribe. Nothing to install.

What risk level is os_wait? +

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

Can I rate-limit os_wait? +

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

How do I block os_wait completely? +

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

What MCP server provides os_wait? +

os_wait is provided by the OScribe MCP server (mikealkeal/oscribe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.