Securing AI-based development workflows | Made for Dev Show Ep. 2
In this second episode of the Made for Dev Show specials with @DockerInc host Sammy sits down with Oleg Ε elajev from Docker's Developer Relations team to discuss securing AI-based development workflows.
π Core Topics Covered Docker Hardened Images (DHI): Oleg introduces DHI, which are minimal, production-ready images for popular open-source technologies (like Node.js, Python, etc.). These images are monitored to maintain near-zero CVEs (Common Vulnerabilities and Exposures) and are now free for developers [01:18], [05:26].
π Docker Sandboxes (VM-based): Building on the previous episode, Oleg demonstrates the new VM-based architecture for Docker Sandboxes. This creates an isolated virtual machine for AI agents (like Claude or Gemini), preventing them from "nuking" the host root directory or leaking sensitive local data [10:55], [11:54].
π Network Proxy & Key Injection: A key security feature where the AI agent inside the sandbox never actually "sees" the API keys. Instead, a network proxy managed by Docker injects the credentials into outgoing requests, protecting your secrets from prompt injection attacks [14:37].
π Securing MCP (Model Context Protocol): Discussion on how the MCP Toolkit/Gateway acts as a security proxy. Oleg shows how you can use "interceptors" (shell scripts) to monitor, log, or even block specific tool calls (e.g., preventing an agent from accessing unauthorized GitHub repositories) [17:51], [23:45].
β¨ Key Highlights
YOLO Mode Protection: Even if you run your AI agents in "YOLO mode" (skipping permissions), the sandbox provides a "blast radius" that protects your host machine [12:53].
Granular Network Control: Demonstrating how to block specific domains (like ubuntu.com) at the sandbox level to prevent unauthorized downloads or data exfiltration [15:07].
MCP Gateway Versatility: The gateway supports both stdio and HTTP transports, allowing it to be deployed as a central proxy for an entire team's AI tools [26:05].
