proxmox_list_all_vms_from_all_clusters
List ALL VMs from ALL configured clusters.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-list-all-vms-from-all-clusters.md
What proxmox_list_all_vms_from_all_clusters does on MCP Proxmox Server
AI agents call proxmox_list_all_vms_from_all_clusters to retrieve information from MCP Proxmox Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why proxmox_list_all_vms_from_all_clusters is rated Low
This tool retrieves and enumerates virtual machine information across all clusters without modifying, deleting, or executing any operations. However, the severity is elevated to 'medium' rather than 'low' because listing all VMs across all clusters could expose sensitive infrastructure details (hostnames, resource allocation, deployment topology) that could be valuable for reconnaissance or planning targeted attacks…
From the tool's definition Tool name contains 'list' and description states 'List ALL VMs from ALL configured clusters' — a query operation that retrieves data with no side effects.
Attacks that exploit this kind of access
The rule that runs proxmox_list_all_vms_from_all_clusters 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_list_all_vms_from_all_clusters, this is the rule to start with:
proxmox_list_all_vms_from_all_clusters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_list_all_vms_from_all_clusters call is checked against it from then on.
Questions about proxmox_list_all_vms_from_all_clusters
List ALL VMs from ALL configured clusters. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_list_all_vms_from_all_clusters: 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.
proxmox_list_all_vms_from_all_clusters 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_all_vms_from_all_clusters 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_all_vms_from_all_clusters. 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_all_vms_from_all_clusters 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.
More on MCP Proxmox Server, and thousands of servers like it.
This server
Across the catalogue