High-risk tools in Autodock
7 of the 27 tools in Autodock 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
-
browser.listenExecuteStart a browser listener to capture console logs, network requests, and errors from the user's browser. After starting, provide the user with the console command to paste in th...
-
env.emailExecuteDocumentation for receiving emails in an Autodock environment. Each environment can receive emails at *@{slug}.autodock.io. Emails are delivered via HTTPS webhook (SES -> Verce...
-
env.exposeExecuteExpose a port on an environment with a public HTTPS URL. Creates https://<name|port>--<slug>.<base-domain>. Returns URL and .env update guidance. IMPORTANT: After exposing a p...
-
env.gh_runnerExecuteDocumentation for configuring and running a GitHub Actions self-hosted runner. The GitHub Actions runner is pre-installed at /opt/actions-runner. To use it: 1. Get a registrati...
-
env.restartExecuteRestart a stopped environment. Boots the same instance with preserved storage.
-
env.runExecuteREQUIRED before executing commands on an Autodock environment. ALWAYS call this tool before using SSH to run commands - it provides: • SSH key path and connection string • CRIT...
-
env.stopExecuteStop (power down) an environment. Safe to restart later.
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.