get_vm_vncproxy
Create a VNC proxy connection ticket for a VM (for console access).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-vm-vncproxy.md
What get_vm_vncproxy does on Proxmox MCP Server
AI agents invoke get_vm_vncproxy to trigger actions in Proxmox 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 get_vm_vncproxy is rated High
This tool does more than read data; it creates an active VNC proxy session that enables console-level access to a virtual machine. While it doesn't modify VM state directly, it establishes an interactive session that could be misused to gain full control over the VM's operating system.
From the tool's definition 'Create a VNC proxy connection ticket for a VM (for console access)' — actively creates a proxy session/ticket, triggering an external operation granting console access to a VM.
Attacks that exploit this kind of access
The rule that runs get_vm_vncproxy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_vm_vncproxy, this is the rule to start with:
get_vm_vncproxy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every get_vm_vncproxy call is checked against it from then on.
Questions about get_vm_vncproxy
Create a VNC proxy connection ticket for a VM (for console access). It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_vm_vncproxy: 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 Proxmox MCP Server. Nothing to install.
get_vm_vncproxy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the get_vm_vncproxy 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.
Set action: deny in the PolicyLayer policy for get_vm_vncproxy. 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.
get_vm_vncproxy is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue