proxmox_windows_execute_command

Execute command on Windows VM via QEMU guest agent.

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox

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/bsahane-mcp-proxmox/proxmox-windows-execute-command.md

WHAT IT DOES

What proxmox_windows_execute_command does on MCP Proxmox Server

AI agents invoke proxmox_windows_execute_command to trigger actions in MCP Proxmox 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 proxmox_windows_execute_command is rated High

This tool runs code/commands on guest VMs with effects entirely dependent on the command arguments. An AI agent could execute destructive commands (format disks, delete files, disable security, pivot to other systems) making it critical severity. The blast radius spans entire VM compromise and potential lateral movement in the infrastructure.

From the tool's definition Tool name contains 'execute_command' and description states 'Execute command on Windows VM via QEMU guest agent.' This directly executes arbitrary commands on virtualized systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxmox_windows_execute_command safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_windows_execute_command, this is the rule to start with:

proxmox_windows_execute_command Rate-limited

proxmox_windows_execute_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": {
    "proxmox_windows_execute_command": {
      "limits": [
        {
          "counter": "proxmox_windows_execute_command_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 MCP Proxmox Server, apply this rule, and every proxmox_windows_execute_command call is checked against it from then on.

FAQ

Questions about proxmox_windows_execute_command

What does the proxmox_windows_execute_command tool do? +

Execute command on Windows VM via QEMU guest agent. It is categorised as a Execute tool in the MCP Proxmox 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 proxmox_windows_execute_command? +

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

What risk level is proxmox_windows_execute_command? +

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

Can I rate-limit proxmox_windows_execute_command? +

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

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

proxmox_windows_execute_command is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

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

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server →adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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