KernDocs
KernGitHub ↗

Internet firewall

Allow a site or service

Configure internet connections once, then reuse them across your agents.

Choose the access path

For structured actions such as reading email, first check for a bundled tool. For direct web requests, CLIs or package downloads, configure a network integration. These paths have separate controls.

Open Home → Integrations and use the built-in guide for the service. It carries the current account, credential and scope requirements.

Allow only the access the task needs

  1. 1
    Enable an existing integration

    Choose the managed integration for a known service and configure the available restrictions. Connect an account if required.

  2. 2
    Add a domain rule when needed

    For another public site, add its exact hostname and allowed methods or paths under Custom Domain Access. Redirects to a different host need their own permission.

  3. 3
    Try one narrow request

    Ask the agent to perform the intended read or action. Inspect Network audit for direct requests, or Tool audit for bundled tools.

  4. 4
    Read a denial before changing policy

    Use its reason to correct the specific missing rule, scope or account state. Grant only access you intend; a denial is not permission to route around the firewall.

Enabling a network integration does not grant a bundled tool action, and connecting an account does not authorize every operation on it. See Approvals.

Understand the boundary

The internet firewall explanation describes the proxy, HTTPS inspection and tool-service path. For failures, start with network troubleshooting.