AI agents call dokploy_get_application 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.
The tool retrieves application configuration metadata without any side effects. It explicitly excludes sensitive data (environment variables and secrets) and provides read-only access to application state. No data is created, modified, deleted, or executed—only queried. This is a standard Read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name includes 'get' and description states 'Get application config by ID. Returns status, git provider config, and other fields.' This is a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get application config by ID. Returns status, git provider config, and other fields. Environment variables and secrets are excluded; use dokploy_list_environment to access those. 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_application: 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_application 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_application 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_application. 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_application 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 →