Bash

The Flaw in the Modern Sandbox Traditional sandboxing relies on isolation—placing an agent inside a virtual machine or container to prevent it from harming the host. However, this approach often overlooks the vulnerability of the credentials used within that environment. To function, an agent needs permissions, typically granted through API keys or OIDC tokens. If these secrets reside inside the sandbox, they are susceptible to exfiltration or misuse by increasingly clever Large Language Models. The sandbox may isolate the execution, but it fails to secure the access tokens that are the keys to the kingdom. Remy Guercio argues that true security requires separating execution isolation from access control. When permissions are bundled with the agent, the boundary remains porous. By shifting identity to the network layer, we can remove the risk of credential theft entirely, ensuring that the agent never actually touches the real keys it uses to communicate with external providers. Network Identity as a Security Boundary Using the WireGuard protocol, Tailscale enables a system where every network connection carries a verified identity. This identity isn't just an IP address; it includes the user, group, or specific tags associated with the device or process. When an agent runs in a GitHub Actions runner, for example, it can be assigned a specific tag on the network. This architecture allows for a radical shift in how we handle LLM access. Instead of passing an Anthropic or OpenAI key to the agent, the agent connects to a network node that handles the authentication. The connection itself is the proof of identity. Because the Tailscale control plane guarantees the identity of the node, the receiving service knows exactly who is making the request without needing a secret token to be passed through the application code. Aperture and the LLM Gateway Aperture serves as the practical implementation of this philosophy. It acts as an AI gateway that sits on the tailnet, accepting requests from agents that have no real API keys. In the agent's configuration, the developer simply provides a placeholder dash where a key would normally go. The agent points to the Aperture base URL, and the gateway uses the incoming Tailscale identity to apply permissions and quotas. This setup provides unprecedented visibility. Because all traffic must flow through the gateway at the network level, administrators can see every tool call, bash command, and Model Context Protocol request. This visibility is not achieved through internal instrumentation—which can be bypassed—but through a mandatory network path. If an agent tries to execute a malicious command or exceed its budget, the network layer simply cuts the connection. Building Identity-Aware Services with TSnet For developers looking to build their own internal tools, Tailscale provides TSnet, an open-source library that allows Go programs to become full nodes on a tailnet. This enables the creation of custom, identity-aware services like internal MCP servers or API endpoints without the overhead of OAuth or complex credential management. By embedding the network stack directly into the application, developers can query the identity of any incoming connection. This makes it possible to enforce granular access controls—such as limiting specific GPU resources to certain engineering teams—while maintaining a seamless developer experience. The network becomes the primary source of truth for both connectivity and authorization. Summary and the Future of Access Control Shifting sandboxing to the network layer solves the fundamental problem of "toys in the sandbox." By removing credentials from the execution environment, organizations can empower agents to perform complex tasks without the fear of secret leakage. As agents move toward more autonomous behaviors and direct code execution, having a robust, identity-aware network boundary will be the only way to maintain control over the AI ecosystem.