get_container_feature
Check if a feature is available for a container (snapshot, clone, copy).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-container-feature.md
What get_container_feature does on Proxmox MCP Server
AI agents call get_container_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_container_feature is rated Low
This tool performs a read-only check of container feature availability. It returns information about whether certain capabilities (snapshot, clone, copy) are supported for a container without creating, modifying, deleting, or executing any operations. The use of 'check' and 'available' indicates a query/inspection action with no side effects.
From the tool's definition Tool name 'get_container_feature' with description 'Check if a feature is available for a container' indicates a query operation that retrieves or checks feature availability without modifying state.
Attacks that exploit this kind of access
The rule that runs get_container_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_container_feature, this is the rule to start with:
get_container_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_container_feature call is checked against it from then on.
Questions about get_container_feature
Check if a feature is available for a container (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_container_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_container_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_container_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_container_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_container_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