REQUIRED 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 • CRITICAL: nohup backgrounding pattern (</dev/null) to prevent SSH hangs • mise-managed tool activation (node, npm, python, p...
Accepts file system path (cwd); Accepts freeform code/query input (command)
Part of the Autodock MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke env.run to trigger processes or run actions in Autodock. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
env.run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
env.run:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Autodock policy for all 27 tools.
Agents calling execute-class tools like env.run have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
env.run is one of the high-risk operations in Autodock. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
REQUIRED 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 • CRITICAL: nohup backgrounding pattern (</dev/null) to prevent SSH hangs • mise-managed tool activation (node, npm, python, pip, go, etc. need bash -li -c wrapper) • Vite host validation fix (__VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS) • HTTP proxy setup for traffic logging • Log file locations for Loki capture Returns SSH connection details and command templates. Does NOT execute commands directly. After calling this tool, use the provided command patterns with Bash. If environmentId omitted, auto-selects when exactly one running env exists.. It is categorised as a Execute tool in the Autodock MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for env.run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.
env.run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the env.run rule in your Intercept 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 Intercept policy for env.run. 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.
env.run is provided by the Autodock MCP server (mikesol/autodock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept