system_wait

What system_wait does on Claude Mobile

AI agents invoke system_wait to trigger actions in Claude Mobile. 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 system_wait is rated High

This tool triggers an external operation (a system-level delay) whose effect depends on the argument (duration in milliseconds). It is not merely retrieving data (Read), nor creating/modifying reversible data (Write), nor permanently destroying data (Destructive), nor moving money (Financial). It fits Execute because it runs an operation with side effects on system state/timing.

From the tool's definition The tool name 'system_wait' and description 'Wait for specified duration (ms)' indicate it executes a timed delay operation. While described as a wait function, this is an executable action that controls program flow and timing in mobile automation contexts.

Risk signalsAdmin/system-level operation

The rule that runs system_wait safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_wait, this is the rule to start with:

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

Questions about system_wait