AI agents call dokploy_get_compose 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 and queries compose stack configuration data without modifying, deleting, or executing any operations. It is a straightforward read operation that returns information. The blast radius of misuse is minimal — an attacker gains visibility into compose stack configuration but cannot alter deployments or infrastructure.
From the tool's definition Tool name 'dokploy_get_compose' with description 'Get compose stack config by ID' — the verb 'Get' and action of retrieving configuration data indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get compose stack config by 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_compose: 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_compose 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_compose 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_compose. 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_compose 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.
dokploy_get_compose is one line of Dokploy's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →