> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemoclaw/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.

# Customize the Sandbox Network Policy

> Choose the supported workflow for changing sandbox network access.

Choose the policy workflow that matches the scope and persistence of the network access change.
NemoClaw declares sandbox policy in YAML, and [NVIDIA OpenShell](https://github.com/NVIDIA/OpenShell) enforces it at runtime.

| Goal                                                     | Use this workflow                                                                       |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Change every future sandbox for an agent                 | [Change the Baseline Network Policy](configure-policies/change-baseline-network-policy) |
| Add or remove a maintained preset for one sandbox        | [Apply Policy Presets](configure-policies/apply-policy-presets)                         |
| Add a reviewed endpoint that no maintained preset covers | [Create Custom Policy Presets](configure-policies/create-custom-policy-presets)         |
| Allow direct TLS negotiation for an exact endpoint       | [Configure Raw TLS Passthrough](configure-policies/configure-raw-tls-passthrough)       |
| Replace the complete live policy                         | [Replace the Live Network Policy](configure-policies/replace-live-network-policy)       |
| Give the sandbox agent a redacted policy summary         | [Explain Network Policy to Agents](explain-network-policy-to-agents)                    |
| Approve or deny one blocked request                      | [Approve or Deny Network Requests](approve-network-requests)                            |

If a sandbox needs an HTTP service on the host, expose the service on a host IP that the OpenShell gateway can reach.
Apply a custom preset with `nemohermes <sandbox> policy add --from-file`.
Do not rely on `host.docker.internal` as a general host-service path because it bypasses the OpenShell policy path and may not be reachable.
Refer to [Agent cannot reach a host-side HTTP service](../reference/troubleshooting#agent-cannot-reach-a-host-side-http-service).

Adding a host to the egress policy permits a connection only when the endpoint, port, method, and binary rules match.
OpenShell applies SSRF protection separately.
It can deny a request when the final address resolves to a loopback, private, link-local, or blocked internal range.
If a package installer or browser download still fails after you allow the public host, install the binary at build time.
Use [`nemohermes onboard --from`](../reference/commands#--from-dockerfile) instead of runtime egress.

## Static Changes

<a id="prerequisites" />

<a id="edit-the-policy-file" />

<a id="re-run-onboard" />

<a id="verify-the-policy" />

<a id="add-blueprint-policy-additions" />

Static changes modify the policy source that NemoClaw reads during sandbox creation.
Follow [Change the Baseline Network Policy](configure-policies/change-baseline-network-policy) to edit the agent policy file, rerun onboarding, and verify the result.

## Dynamic Changes

<a id="scope-of-dynamic-changes" />

<a id="add-a-preset-file-with-policy-add-recommended" />

Dynamic changes update a running sandbox.
Use [Apply Policy Presets](configure-policies/apply-policy-presets) for reviewed additions that NemoClaw records and replays.

<a id="approve-requests-interactively" />

Use [Approve or Deny Network Requests](approve-network-requests) for one-off access.
Use [Replace the Live Network Policy](configure-policies/replace-live-network-policy) only when a preset cannot express the complete change.

## Policy Presets

Maintained policy presets cover common integrations and package services.
Follow [Apply Policy Presets](configure-policies/apply-policy-presets) to preview, apply, reapply, list, or remove them.
For guided service workflows, refer to [Common Integration Policy Examples](integration-policy-examples).

## Custom Preset Files

<a id="authoring" />

<a id="apply-a-single-file" />

<a id="apply-every-file-in-a-directory" />

<a id="remove-a-custom-preset" />

<a id="custom-recipe-url-based-mcp-server" />

Custom preset files add reviewed endpoint access without changing the baseline.
Follow [Create Custom Policy Presets](configure-policies/create-custom-policy-presets) to author, validate, apply, and remove a custom preset.
That page also contains the URL-based MCP server recipe formerly located in this guide.

## Raw TLS Passthrough

<a id="custom-recipe-for-raw-tls-passthrough-with-tls-skip" />

Some endpoints require direct TLS negotiation and fail through inspected L7 proxying.
Follow [Configure Raw TLS Passthrough](configure-policies/configure-raw-tls-passthrough) for the bounded `access: full` and `tls: skip` recipe.

## Live Policy Replacement

<a id="export-edit-and-set-the-base-policy" />

OpenShell `policy set` replaces the complete live policy.
Follow [Replace the Live Network Policy](configure-policies/replace-live-network-policy) to export the round-trippable base, preserve existing entries, and apply a validated replacement.

## Agent Policy Context

Agents need a redacted view of active presets and policy verification state.
Follow [Explain Network Policy to Agents](explain-network-policy-to-agents) to print or refresh that context and interpret failure classifications.

## Related Topics

* [Common Integration Policy Examples](integration-policy-examples) provides maintained service workflows.
* [Network Policies](../reference/network-policies) is the canonical policy reference.
* [OpenShell Policy Schema](https://docs.nvidia.com/openshell/latest/reference/policy-schema.html) provides the complete YAML schema.
* [OpenShell Sandbox Policies](https://docs.nvidia.com/openshell/latest/sandboxes/policies.html) explains OpenShell-layer policy iteration.