# Giving AI agents network access without getting owned > Source: > Published: 2026-08-04 01:37:16+00:00 Cross-post. Original: [stellarbytecapital.com/blog/ai-agent-network-egress-control] Most useful AI agents need the network. They fetch market data, call an API, hit a database. But the moment your sandbox can reach the open internet, you've built the exact channel an attacker needs to exfiltrate data or pull a payload. Network egress is where a contained breach turns into a real one — and it's the control teams skip most often. Think about what a compromised agent actually needs to cause damage. It can read data in its sandbox, sure. But to *exfiltrate* it, it needs a network path off the box. Cut that path, and a "successful" compromise has nowhere to send anything. **An escaped agent with no egress is mostly harmless.** Isolation stops the code from breaking out; egress control stops the data from getting out. You want both. **The sandbox starts with zero outbound network. You open specific destinations the task genuinely needs, and nothing else.** You can't enumerate every bad destination, but you *can* enumerate the handful of good ones a task actually requires. Locking down egress doesn't replace isolation — it complements it. The controls stack: disposable per-run isolation, least privilege, no secrets in the sandbox, *and* default-deny egress. Each closes a door the others don't. Give the agent exactly the network it needs for the task in front of it — and not one destination more. We're **Xingyao Byte** — building secure AI-execution layers, quant trading systems, and payment platforms. Remote, async-first → [stellarbytecapital.com](https://www.stellarbytecapital.com/)