screen_wait · Screen Agent MCP: Risk & Policy

WHAT IT DOES

What screen_wait does on Screen Agent

AI agents invoke screen_wait to trigger actions in Screen Agent. 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 screen_wait needs a policy

While this tool primarily pauses execution and doesn't directly modify data, it is an Execute action because it can control timing of subsequent desktop automation operations. The tool's effect depends on arguments (wait duration) and controls the flow of automated interactions.

From the tool's definition Tool name 'screen_wait' and description '等待指定时间，用于等待界面加载或动画完成' (Wait for specified time, used for waiting for interface loading or animation completion) indicate time-delay execution functionality that can trigger external operations dependent on timing…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

screen_wait Rate-limited

screen_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": {
    "screen_wait": {
      "limits": [
        {
          "counter": "screen_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 Screen Agent, so you can run agents against it safely.

FAQ

Questions about screen_wait

What does the screen_wait tool do? +

等待指定时间，用于等待界面加载或动画完成。. It is categorised as a Execute tool in the Screen Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screen_wait? +

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

What risk level is screen_wait? +

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

Can I rate-limit screen_wait? +

Yes. Add a rate_limit block to the screen_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 screen_wait completely? +

Set action: deny in the PolicyLayer policy for screen_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 screen_wait? +

screen_wait is provided by the Screen Agent MCP server (lqszhsp/screen-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.