This record as markdown: /tools/aapanel-mcp/docker-container-list.md
What docker_container_list does on Aapanel
AI agents call docker_container_list to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why docker_container_list is rated Low
This tool retrieves Docker container metadata without creating, modifying, or deleting any resources. It is a read-only query operation that returns container information. The severity is low because listing containers exposes operational details but does not enable direct system compromise or data modification.
From the tool's definition Tool name is 'docker_container_list' and description states 'List all Docker containers.' The verb 'list' and action of retrieving/querying container information with no modifications.
Attacks that exploit this kind of access
The rule that runs docker_container_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_container_list, this is the rule to start with:
docker_container_list 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 Aapanel, apply this rule, and every docker_container_list call is checked against it from then on.
Questions about docker_container_list
List all Docker containers. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for docker_container_list: 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 Aapanel. Nothing to install.
docker_container_list 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 docker_container_list 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 docker_container_list. 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.
docker_container_list is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue