get_container_status

Get the current runtime status of a 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-status.md

WHAT IT DOES

What get_container_status does on Proxmox MCP Server

AI agents call get_container_status 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.

RISK

Why get_container_status is rated Low

This tool retrieves and reports the current runtime status of a container—a pure read operation with no capability to modify, execute, or delete resources. The blast radius of misuse is minimal; an agent could only gather information about container state, not take actions or cause harm.

From the tool's definition Tool name 'get_container_status' and description 'Get the current runtime status of a container' indicate a query operation that retrieves state information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_container_status 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_status, this is the rule to start with:

get_container_status Allowed

get_container_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_container_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every get_container_status call is checked against it from then on.

FAQ

Questions about get_container_status

What does the get_container_status tool do? +

Get the current runtime status of a 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_status? +

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

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

Can I rate-limit get_container_status? +

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

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

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

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →