AI agents call dokploy_get_containers to retrieve information from Dokploy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves container information without modifying, executing, or deleting any resources. It falls squarely into the Read category. Severity is medium rather than low because container metadata can reveal infrastructure topology, running services, and deployment details that could inform follow-up attacks or reconnaissance, making the blast radius moderate for an untrusted agent.
From the tool's definition Tool name and description indicate listing/retrieving Docker container data: 'List all Docker containers. Optionally filter by server ID.' The verb 'List' and lack of modification language confirm this is a retrieval operation.
Attacks that exploit this kind of access
List all Docker containers. Optionally filter by server ID. It is categorised as a Read tool in the Dokploy MCP Server, which means it retrieves data without modifying state.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_get_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 Dokploy. Nothing to install.
dokploy_get_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 dokploy_get_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 dokploy_get_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.
dokploy_get_containers is provided by the Dokploy MCP server (wyattjoh/dokploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →