docker-containers
List Docker containers on the host system
This record as markdown: /tools/0xshariq-docker-mcp-server/docker-containers.md
What docker-containers does on Docker MCP Server
AI agents call docker-containers to retrieve information from Docker 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 docker-containers is rated Low
This tool queries Docker container information with no side effects. Listing containers is a non-destructive, informational operation. While it could expose information about running services, the severity is low because it performs no actions, creates no data, and cannot be misused to cause damage. Confidence is high due to explicit 'List' language in the description.
From the tool's definition Tool name 'docker-containers' and description 'List Docker containers on the host system' indicate a read-only operation that retrieves container state without modification.
Attacks that exploit this kind of access
The rule that runs docker-containers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker-containers, this is the rule to start with:
docker-containers 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 Docker MCP Server, apply this rule, and every docker-containers call is checked against it from then on.
Questions about docker-containers
List Docker containers on the host system. It is categorised as a Read tool in the Docker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for docker-containers: 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 Docker MCP Server. Nothing to install.
docker-containers 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-containers 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-containers. 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-containers is provided by the Docker MCP Server MCP server (0xshariq/docker-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker MCP Server, and thousands of servers like it.
This server
Across the catalogue