// MCP TOOL REFERENCE

AUTODOCK TOOLS

27 tools from the Autodock MCP Server, categorised by risk level.

// ALL 27 AUTODOCK TOOLS

READ 14 tools

Read account.info Return information about the currently authenticated Autodock user Read account.list_api_keys List your API keys (shows prefix only, not full key) Read browser.poll Retrieve captured browser events from a listener session. Returns console logs, network requests, and erro... Read browser.shot Request a screenshot from the browser. The screenshot will be captured asynchronously by the browser. IMPO... Read browser.stop Stop a browser listener session. This will signal the browser to stop capturing and clean up server resour... Read env.extend Extend the auto-stop timer for a running environment. Resets the idle timer and sets a new auto-stop duration. Read env.launch Launch a new Autodock environment. Typically takes 1-2 minutes. Read env.list List environments for the authenticated user Read env.listExposed List exposed ports for an environment Read env.observe Get Loki query commands for observing logs on an Autodock environment. Returns SSH+curl commands for query... Read env.reserve Preview the cost of reserving an environment for 30 days ($149). Reserved environments do not auto-stop and... Read env.reserve_confirm Confirm reservation and process $149 payment. Environment will not auto-stop for 30 days after reservation.... Read env.save Get templates for saving session setup to AUTODOCK.md. Returns environment details, exposed ports, and com... Read env.status Fetch a specific environment by ID

WRITE 3 tools

Write account.create_api_key Create a new API key for headless MCP authentication. The key will be shown ONCE - make sure to save it se... Write env.get_ssh_key Fetch a fresh download URL for the SSH private key. Use this if the key was corrupted during initial save (... Write env.sync REQUIRED before syncing files to an Autodock environment. Provides SSH connection details and rsync templa...

DESTRUCTIVE 3 tools

Destructive account.revoke_api_key Revoke an API key by ID. The key will immediately stop working. Destructive env.destroy Destroy an environment permanently. Destructive env.unexpose Remove an exposed port from an environment

EXECUTE 7 tools

Execute browser.listen Start a browser listener to capture console logs, network requests, and errors from the user's browser. Af... Execute env.email Documentation for receiving emails in an Autodock environment. Each environment can receive emails at *@{s... Execute env.expose Expose a port on an environment with a public HTTPS URL. Creates https://<name|port>--<slug>.<base-domain>... Execute env.gh_runner Documentation for configuring and running a GitHub Actions self-hosted runner. The GitHub Actions runner i... Execute env.restart Restart a stopped environment. Boots the same instance with preserved storage. Execute env.run REQUIRED before executing commands on an Autodock environment. ALWAYS call this tool before using SSH to r... Execute env.stop Stop (power down) an environment. Safe to restart later.

// FAQ

How many tools does the Autodock MCP server have? +

The Autodock MCP server exposes 27 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Autodock tools? +

Route the Autodock server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Autodock tools fall into? +

Autodock tools are categorised as Read (14), Write (3), Destructive (3), Execute (7). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.