send_vm_monitor_command

Send a QEMU monitor command to a VM (advanced/low-level).

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/send-vm-monitor-command.md

What send_vm_monitor_command does on Proxmox MCP Server

AI agents invoke send_vm_monitor_command 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 send_vm_monitor_command is rated High

QEMU monitor commands are low-level control commands sent directly to the VM hypervisor. These can execute arbitrary operations including stopping VMs, modifying memory, injecting keystrokes, manipulating block devices, or even destroying guest state. This is an execute-level capability with critical blast radius since misuse could compromise or destroy running virtual machines and their workloads.

From the tool's definition Send a QEMU monitor command to a VM (advanced/low-level)

Questions about send_vm_monitor_command

What does the send_vm_monitor_command tool do? +

Send a QEMU monitor command to a VM (advanced/low-level). 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 send_vm_monitor_command? +

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

What risk level is send_vm_monitor_command? +

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

Can I rate-limit send_vm_monitor_command? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.