This record as markdown: /tools/eaveluo-1panel-mcp/get-container-status.md
What get_container_status does on 1Panel MCP Server
AI agents call get_container_status to retrieve information from 1Panel 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_status is rated Low
This tool performs a read-only retrieval of container status information. It has no side effects and does not create, modify, delete, or execute any operations. The blast radius is minimal since it only exposes visibility into existing infrastructure state, which an AI agent cannot misuse to cause harm through this tool alone.
From the tool's definition Tool name 'get_container_status' and description 'Get containers status' indicate a query operation that retrieves the current state of Docker containers without modifying, deleting, or executing any container commands.
Attacks that exploit this kind of access
The rule that runs get_container_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel 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 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 1Panel MCP Server, apply this rule, and every get_container_status call is checked against it from then on.
Questions about get_container_status
Get containers status. It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1Panel 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 1Panel MCP Server. Nothing to install.
get_container_status 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_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.
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.
get_container_status is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue