compose-ps
Lists Docker Compose services with structured state and status information.
This record as markdown: /tools/io-github-dave-london-npm/compose-ps.md
What compose-ps does on Npm
AI agents call compose-ps to retrieve information from Npm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why compose-ps is rated Low
This tool performs a listing/query operation similar to 'docker-compose ps', which retrieves and reports the current state of services. No data is created, modified, deleted, or executed. The operation has no side effects and requires no external execution. This is a straightforward informational read operation with minimal risk.
From the tool's definition Tool name 'compose-ps' and description 'Lists Docker Compose services' indicates a read-only query operation that retrieves structured status information without modifying state.
Attacks that exploit this kind of access
The rule that runs compose-ps safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compose-ps, this is the rule to start with:
compose-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 Npm, apply this rule, and every compose-ps call is checked against it from then on.
Questions about compose-ps
Lists Docker Compose services with structured state and status information. It is categorised as a Read tool in the Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm MCP server in PolicyLayer and add a rule for compose-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 Npm. Nothing to install.
compose-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 compose-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 compose-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.
compose-ps is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue