get_vm_feature
Check if a specific feature is available/supported for a VM (e.g. snapshot, clone, copy).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-vm-feature.md
What get_vm_feature does on Proxmox MCP Server
AI agents call get_vm_feature to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_vm_feature is rated Low
This tool merely queries and returns whether a VM supports certain features (snapshot, clone, copy). It has no side effects, does not execute operations, and does not modify any state. It is a straightforward information-retrieval operation, fitting the Read category. The blast radius is minimal—misuse would only return incorrect feature availability information, causing no operational damage.
From the tool's definition Tool name 'get_vm_feature' and description 'Check if a specific feature is available/supported for a VM' indicate a read-only query operation that retrieves capability/status information without modifying or executing any actions.
Attacks that exploit this kind of access
The rule that runs get_vm_feature safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_vm_feature, this is the rule to start with:
get_vm_feature 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 Proxmox MCP Server, apply this rule, and every get_vm_feature call is checked against it from then on.
Questions about get_vm_feature
Check if a specific feature is available/supported for a VM (e.g. snapshot, clone, copy). 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_feature: 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_feature 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_feature 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_feature. 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_feature 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.
This server
Across the catalogue