Manage app: create/update/delete
AI agents call application to permanently remove resources in Coolify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the tool name 'application' is generic, the description explicitly lists 'delete' as a capability alongside create and update. Delete operations on applications are irreversible and can cause significant downtime or data loss. Even though Write operations are present (create/update), the presence of delete elevates this to Destructive per the severity hierarchy (Destructive > Execute > Write > Read).
From the tool's definition Tool description states 'create/update/delete' operations on applications. The 'delete' action is irreversible and falls under the Destructive category. Additionally, 'update' operations on infrastructure applications can have severe side effects.
Attacks that exploit this kind of access
Manage app: create/update/delete. It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP server in PolicyLayer and add a rule for 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 Coolify. Nothing to install.
application is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
application is provided by the Coolify MCP server (jurislm/coolify-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 →