This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-ps.md
What docker_ps does on Yaver
AI agents call docker_ps to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why docker_ps is rated Low
This tool only lists/retrieves information about running Docker containers. It performs no mutations, deletions, executions, or side effects. While it exposes system information that could be useful for reconnaissance, the tool itself is purely informational and read-only, making it a Read category risk with low severity.
From the tool's definition Tool name 'docker_ps' and description 'List running Docker containers' indicate a query operation that retrieves container status without modifying state.
Attacks that exploit this kind of access
The rule that runs docker_ps safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_ps, this is the rule to start with:
docker_ps 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 Yaver, apply this rule, and every docker_ps call is checked against it from then on.
Questions about docker_ps
List running Docker containers. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for docker_ps: 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 Yaver. Nothing to install.
docker_ps 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_ps 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_ps. 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_ps is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue