Deploys an application in Dokploy.
AI agents invoke application-deploy to trigger actions in Dokploy MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Deployment is an Execute action because it triggers external operations (building, pushing code, restarting services) whose effects are environment-dependent and cannot be predicted solely from the tool definition. While not immediately destructive, a malicious or erroneous deployment could corrupt production systems, making this a high-severity Execute risk.
From the tool's definition Tool name 'application-deploy' and description 'Deploys an application in Dokploy' indicates triggering an external operation (deployment) whose effects depend on which application is specified and the current state of the deployment environment.
Attacks that exploit this kind of access
Deploys an application in Dokploy. It is categorised as a Execute tool in the Dokploy MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for application-deploy: 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 MCP Server. Nothing to install.
application-deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the application-deploy 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 application-deploy. 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.
application-deploy is provided by the Dokploy MCP Server MCP server (limehawk/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 →