AI agents call dokploy_list_deployments 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 historical deployment data for informational purposes only. It queries the state of existing deployments without creating, modifying, deleting, or executing any operations. The information returned (status, timestamps, logs, errors) is read-only metadata about past deployments. No resources are created, modified, or destroyed by this operation.
From the tool's definition Tool name uses 'list' and description states it 'List deployments' and 'Returns status, logPath, startedAt, finishedAt, and errorMessage for each deployment' — purely retrieves and queries deployment information with no modification or side effects.
Attacks that exploit this kind of access
List deployments for an application (newest first). Returns status, logPath, startedAt, finishedAt, and errorMessage for each deployment. 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_list_deployments: 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_list_deployments 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_list_deployments 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_list_deployments. 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_list_deployments 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 →