get_container_feature

Check if a feature is available for a container (snapshot, clone, copy).

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_container_feature

What does the get_container_feature tool do? +

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.

How do I enforce a policy on get_container_feature? +

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.

What risk level is get_container_feature? +

get_container_feature is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_container_feature? +

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.

How do I block get_container_feature completely? +

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.

What MCP server provides get_container_feature? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.