Web fetches reach only the hosts you name
A web fetch to a host your org hasn’t named is blocked until someone reviews it.
A fetch, stopped
- Name a host once
- Add a host to the rule’s exceptions and every agent in the org can reach it.
- Allowed once, on purpose
- The agent or person asks from the record. An admin allows it once or for a while, and the retry passes.
- One command, not a blanket pass
- An exception covers the command it was granted for, once or for a while, and the record keeps it.
The Network off the allowlist policy
Outbound fetches to hosts the org has not named.
- It installs as Observe, so you see your own traffic first. Turn it to Block when you are ready.
- Name a host by adding it to the rule's exceptions; until then every outbound fetch is watched.
- A shell command's hosts cannot all be listed, so while this policy is on, shell commands are observed.
Related use cases and clients
- MCP servers off the org listTools from servers your org hasn’t approved are blocked, and text that tries to instruct the agent is flagged.
- Secrets and env filesFile reads and writes of env files, keys and credentials are blocked, and sending them is flagged by the read scan.
- Set up the MCP proxyThe adapter’s proxy wraps each MCP server a client uses, so every tool call passes the same policy.