get_container_stats

A read tool on the 1Panel MCP server.

SERVER1Panel MCP Server SOURCEeaveluo/1panel-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/eaveluo-1panel-mcp/get-container-stats.md

WHAT IT DOES

What get_container_stats does on 1Panel MCP Server

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

RISK

Why get_container_stats is rated Low

This tool retrieves monitoring/observability data about running containers (CPU, memory, network stats, etc.). It has no side effects, does not modify state, does not execute arbitrary code, and does not delete data. It is a straightforward read operation consistent with 'get' and 'fetch' patterns.

From the tool's definition Tool name 'get_container_stats' and description 'Get container stats' indicate a retrieval operation that queries container statistics without modifying or executing actions on containers.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_container_stats Allowed

get_container_stats 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_stats": {}
  }
}

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

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

FAQ

Questions about get_container_stats

What does the get_container_stats tool do? +

get_container_stats is a read tool on the 1Panel MCP Server MCP server. It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_container_stats? +

Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for get_container_stats: 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.

What risk level is get_container_stats? +

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

Can I rate-limit get_container_stats? +

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

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

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

KEEP EXPLORING

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

This server

All 286 1Panel MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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