get_vm_status
AI agents call get_vm_status to retrieve information from Proxmox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves VM status information without modifying any state. It is part of a read-only Proxmox monitoring interface. Even if misused by an agent, it cannot create, modify, delete, or execute operations—only exposing existing status data. Blast radius is minimal (information disclosure only).
From the tool's definition Tool named 'get_vm_status' with sibling tools including 'get_vm_info', 'get_vm_metrics', 'list_vms', and 'get_cluster_status'. Server description explicitly states 'read-only interaction' and lists monitoring/status checking as primary functions.
Attacks that exploit this kind of access
get_vm_status. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_vm_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_vm_status 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_status. 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_status is provided by the Proxmox MCP Server MCP server (teomarcdhio/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →