vnc_system_command · VNC MCP Server MCP: Risk & Policy

WHAT IT DOES

What vnc_system_command does on VNC MCP Server

AI agents invoke vnc_system_command 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_system_command needs a policy

This tool directly executes shell commands on the target system, which can invoke any program, modify files, exfiltrate data, or compromise system security depending on the shell command argument. The blast radius is unrestricted and critical.

From the tool's definition Tool explicitly performs 'Execute a shell command in the background on the server' — this runs arbitrary code on a remote system via VNC.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vnc_system_command Rate-limited

vnc_system_command 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_system_command": {
      "limits": [
        {
          "counter": "vnc_system_command_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_system_command

What does the vnc_system_command tool do? +

Execute a shell command in the background on the server. 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_system_command? +

Register the VNC MCP Server MCP server in PolicyLayer and add a rule for vnc_system_command: 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_system_command? +

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

Can I rate-limit vnc_system_command? +

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

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

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