AI agents call proxmox_list_vms to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about virtual machines and containers without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal risk; the only concern is information disclosure, which is low severity in a homelab context where the user controls access to this MCP server.
From the tool's definition Tool name 'proxmox_list_vms' and description 'List all VMs (QEMU) and LXC containers' indicate a query/retrieval operation with no modification of state.
Attacks that exploit this kind of access
List all VMs (QEMU) and LXC containers on the configured Proxmox node. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for proxmox_list_vms: 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 Homelab. Nothing to install.
proxmox_list_vms 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 proxmox_list_vms 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 proxmox_list_vms. 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.
proxmox_list_vms is provided by the Homelab MCP server (nainounen/homelab-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 →