High-risk tools in Denkopsai
5 of the 28 tools in Denkopsai are classified as high 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 high risk
-
deployExecutePack the current project directory and deploy it to DenkOps, returning the live URL. No setup needed: if there is no denkops.json, one is inferred from the directory (name, slug...
-
loginExecuteLog in to DenkOps by approving a pairing in your browser (opens app.denkops.com). Run this if a deploy says you're not logged in.
-
redeployExecuteRe-run the current version of a DenkOps project (applies staged env changes / restarts the app). No code re-upload; reuses the last build.
-
start_projectExecuteStart a stopped DenkOps deployment again (reactivates its active version).
-
stop_projectExecuteStop a DenkOps deployment (containers stop and it goes offline). Reversible with start_project.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.