This record as markdown: /tools/io-github-portel-dev-ncp/list-containers.md
What list_containers does on Ncp
AI agents call list_containers to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_containers is rated Low
This tool performs a read-only query of Docker container metadata. It retrieves information about running or existing containers without side effects, mutations, or code execution. The blast radius of misuse is minimal—an AI agent could only enumerate containers, which may expose some infrastructure details but cannot modify state or trigger actions.
From the tool's definition Tool name 'list_containers' and description 'List Docker containers' indicate a retrieval operation that queries container state without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs list_containers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_containers, this is the rule to start with:
list_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 Ncp, apply this rule, and every list_containers call is checked against it from then on.
Questions about list_containers
List Docker containers. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.
Register the Ncp MCP server in PolicyLayer and add a rule for list_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 Ncp. Nothing to install.
list_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 list_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 list_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.
list_containers is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue