get_container_interfaces

Get network interfaces and IPs of a running container.

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-interfaces.md

What get_container_interfaces does on Proxmox MCP Server

AI agents call get_container_interfaces 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_interfaces is rated Low

This tool queries and returns network interface information and IP addresses from a container. It performs a data retrieval operation with no side effects, no code execution, no destructive actions, and no financial impact. The action is purely informational, making it a Read category tool with low severity.

From the tool's definition Tool name 'get_container_interfaces' and description 'Get network interfaces and IPs of a running container' indicate a read-only retrieval operation with no modification or execution of infrastructure.

Questions about get_container_interfaces

What does the get_container_interfaces tool do? +

Get network interfaces and IPs of a running container. 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_interfaces? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_container_interfaces: 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_interfaces? +

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

Can I rate-limit get_container_interfaces? +

Yes. Add a rate_limit block to the get_container_interfaces 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_interfaces completely? +

Set action: deny in the PolicyLayer policy for get_container_interfaces. 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_interfaces? +

get_container_interfaces 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.