Expose 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 port, you MUST verify connectivity from the LOCAL environment (NOT the remote environment): 1. Run: dig <hostname> +short...
Part of the Autodock MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke env.expose 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.expose 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.expose:
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.expose 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.expose 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.
Expose 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 port, you MUST verify connectivity from the LOCAL environment (NOT the remote environment): 1. Run: dig <hostname> +short (verifies DNS resolution) 2. Run: curl -sI <url> (verifies actual HTTPS connectivity) Both must succeed for the user to connect. If either fails, troubleshoot: - Is the service running? Check with "ss -tlnp | grep <port>" - Is it bound to 0.0.0.0 (not just localhost/127.0.0.1)? - Is the backend serving HTTPS internally? Caddy expects HTTP - disable TLS on the backend. Examples: Argo CD, Kubernetes Dashboard, Grafana (when TLS enabled), Vault UI, Consul UI - Does the service have an HTTPS-based readiness check that's failing? Examples: Argo CD health checks, Istio control plane, cert-manager webhook. 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.expose. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.
env.expose 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.expose 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.expose. 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.expose 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