proxmox_windows_vm_info
Get detailed Windows VM information including RDP access.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-windows-vm-info.md
What proxmox_windows_vm_info does on MCP Proxmox Server
AI agents call proxmox_windows_vm_info 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_windows_vm_info is rated Low
This tool retrieves Windows VM details and RDP access information without modifying or executing anything. It is a Read operation. Severity is elevated to medium (rather than low) because RDP access credentials or connection strings exposed through this tool could be leveraged for unauthorized system access if misused by an AI agent, creating a meaningful blast radius in a virtualized infrastructure context.
From the tool's definition Tool is described as 'Get detailed Windows VM information including RDP access.' The verb 'Get' and phrase 'information' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
The rule that runs proxmox_windows_vm_info 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_vm_info, this is the rule to start with:
proxmox_windows_vm_info 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_windows_vm_info call is checked against it from then on.
Questions about proxmox_windows_vm_info
Get detailed Windows VM information including RDP access. 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_windows_vm_info: 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_windows_vm_info 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_windows_vm_info 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_windows_vm_info. 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_windows_vm_info 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