---
title: Network egress map
description: See which hosts each session contacted through bash, the browser, web tools and MCP, with hosts outside the allowlist or new for the repository flagged.
section: security
order: 90
audience: [user, operator]
sources: [packages/harness/src/egress-map, cli/src/egress-cli.ts, docs/egress-map.md]
features: [security.egress]
---

Every session keeps a map of the hosts it contacted: which ones, through which tool, how often, and what was
refused. Two kinds of host are flagged: hosts outside the allowlist, and hosts new for this repository (no earlier
session in the same checkout reached them). The map is local. It leaves the machine only when you share the session,
and then only the host summary goes.

## Quick start {#quick-start}

```bash
venom egress                       # the newest session's map
venom egress <session> --flagged   # only the flagged hosts (a unique prefix of the id is enough)
venom egress list                  # sessions with a map
venom egress --json
```

```text
019a…: 7 hosts, 2 flagged (allow list: the sandbox's)
! api.unknown-cdn.example        0 ok  bash  (outside the allow list, new for this repo, 3 refused)
! docs.vendor.example            4 ok  web_fetch  (new for this repo)
  registry.npmjs.org            41 ok  bash
  github.com                     6 ok  bash,browser
```

| Argument or flag | What it does |
|---|---|
| `[session]` | A session id or unique prefix (default: the newest) |
| `--flagged` | Only flagged hosts |
| `list` | Sessions with a map |
| `--json` | Machine-readable output |

Exit 0, 1 when there is no map, 2 on usage.

## Where contacts come from {#sources}

| Source | What is seen |
|---|---|
| `bash` | every request and `CONNECT` sandboxed bash sends through the egress proxy, allowed or refused (with the reason). Needs the allowlist network: open network and unsandboxed commands bypass the proxy |
| `browser` | every request the browser venom launched makes (pages and what they load), and the URLs `browser_navigate` opens |
| `web_fetch` | the URL's host |
| `web_search` | your SearxNG host (`VENOM_SEARCH_URL`) |
| `mcp` | the host of a remote (http or sse) MCP server whose tool was called |

Subagents share the parent's proxy, so their contacts go into the parent session's map.

## The flags {#flags}

- **Outside the allowlist**: the session's sandbox allowlist when the network is an allowlist (see
  [Sandbox](/docs/security/sandbox.md#network)), else venom's defaults (package registries, GitHub) plus the hosts you configured:
  your orchestrator and SearxNG.
- **New for this repo**: `~/.venom/egress/known/<repo hash>.json` remembers every host the repository's sessions have
  contacted. The repository is the nearest directory with `.git`, else the working directory. The first session in a
  repository sets the baseline and flags nothing as new.

## Files {#files}

`~/.venom/egress/<session>.json` (0600) is rewritten at the end of each turn and when the session ends, and
continued when the session is resumed. At most 2,000 hosts per session. The directory carries a `.gitignore`, so
checkpoints and `/undo` leave it alone.

## Shared sessions {#shared}

`venom session share` puts the map in the trace after running every host and reason through the same redactor as the
transcript. The shared session's Network tab lists the hosts, flagged ones first, with their sources, request and
refusal counts, and when each was last contacted.

## Related {#related}

- [Sandbox](/docs/security/sandbox.md): the egress proxy and allowlist.
- [Audit, signed actions and compliance](/docs/security/audit.md)
