get_vm_spiceproxy

Create a SPICE proxy connection for a VM console.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-vm-spiceproxy.md

WHAT IT DOES

What get_vm_spiceproxy does on Proxmox MCP Server

AI agents invoke get_vm_spiceproxy 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.

RISK

Why get_vm_spiceproxy is rated High

This tool initiates/creates an active proxy connection to a VM console session, which is an external operation that establishes network connectivity and triggers infrastructure-level actions. It goes beyond merely reading data — it creates a live session. Misuse could allow unauthorized console access to VMs, hence medium severity.

From the tool's definition Create a SPICE proxy connection for a VM console

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_vm_spiceproxy 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_spiceproxy, this is the rule to start with:

get_vm_spiceproxy Rate-limited

get_vm_spiceproxy 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": {
    "get_vm_spiceproxy": {
      "limits": [
        {
          "counter": "get_vm_spiceproxy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every get_vm_spiceproxy call is checked against it from then on.

FAQ

Questions about get_vm_spiceproxy

What does the get_vm_spiceproxy tool do? +

Create a SPICE proxy connection for a VM console. 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.

How do I enforce a policy on get_vm_spiceproxy? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_vm_spiceproxy: 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.

What risk level is get_vm_spiceproxy? +

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

Can I rate-limit get_vm_spiceproxy? +

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

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

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

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →