Critical-risk tools in Coolify MCP Server
10 of the 89 tools in Coolify MCP Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete_applicationDestructiveDelete an application. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_application_envDestructiveDelete an environment variable from an application
-
delete_databaseDestructiveDelete a database. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_environmentDestructiveDelete an environment. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_github_appDestructiveDelete a GitHub App configuration. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_private_keyDestructiveDelete a private key. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_projectDestructiveDelete a project. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_serverDestructiveDelete a server. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_serviceDestructiveDelete a service. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.
-
delete_service_envDestructiveDelete an environment variable from a service
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.