Update application config fields. Only applicationId is required; all other fields are optional. Supports: name, appName, description, dockerfile, dockerContextPath, command, replicas, memoryLimit, cpuLimit, and more.
AI agents use dokploy_update_application to create or update resources in Dokploy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dokploy environment.
This tool modifies application configuration in a reversible manner. While it changes critical deployment settings (dockerfile, command, resource limits), these changes can be reverted by issuing subsequent updates. The high severity reflects that misconfiguration could cause service disruptions, but the Write category is appropriate since the changes are not permanently destructive and can be undone.
From the tool's definition Tool name contains 'update', description states 'Update application config fields' with support for modifying name, dockerfile, dockerContextPath, command, replicas, memoryLimit, cpuLimit, and more.
Attacks that exploit this kind of access
Update application config fields. Only applicationId is required; all other fields are optional. Supports: name, appName, description, dockerfile, dockerContextPath, command, replicas, memoryLimit, cpuLimit, and more. It is categorised as a Write tool in the Dokploy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_update_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_update_application is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dokploy_update_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_update_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_update_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.
dokploy_update_application 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 →