vnc_wait_for_change · VNC MCP Server MCP: Risk & Policy

WHAT IT DOES

What vnc_wait_for_change does on VNC MCP Server

AI agents invoke vnc_wait_for_change to trigger actions in VNC MCP Server. 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 vnc_wait_for_change needs a policy

While vnc_wait_for_change itself is passive (Read-like), it functions within an agentic execution context where an AI observes screen state and triggers subsequent actions. The tool enables conditional execution flows - waiting for a change then proceeding to click, type, or launch applications.

From the tool's definition Tool performs continuous monitoring and conditional triggering based on screen state changes. Part of VNC server suite that 'control[s] computers via VNC' with 'human-like input control.' Waiting for visual changes is a prerequisite to executing subsequent…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vnc_wait_for_change Rate-limited

vnc_wait_for_change 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": {
    "vnc_wait_for_change": {
      "limits": [
        {
          "counter": "vnc_wait_for_change_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 VNC MCP Server, so you can run agents against it safely.

FAQ

Questions about vnc_wait_for_change

What does the vnc_wait_for_change tool do? +

Wait until a region changes. It is categorised as a Execute tool in the VNC MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vnc_wait_for_change? +

Register the VNC MCP Server MCP server in PolicyLayer and add a rule for vnc_wait_for_change: 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 VNC MCP Server. Nothing to install.

What risk level is vnc_wait_for_change? +

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

Can I rate-limit vnc_wait_for_change? +

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

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

vnc_wait_for_change is provided by the VNC MCP Server MCP server (volkan-m/vnc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.