> For the complete documentation index, see [llms.txt](https://handbook.harmonic.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.harmonic.security/handbook/3.-runtime-sandbox-and-autonomy.md).

# 3. Runtime, Sandbox & Autonomy

How to contain what AI agents can do at runtime — sandbox isolation, network egress, browser access, filesystem scope, approvals, and scheduled task governance.

*Last reviewed: August 18, 2026*

{% hint style="info" %}
What an AI agent can do at runtime is as important as what data it can see. Sandbox isolation, network egress controls, browser access policies, and approval gates determine whether an agent's actions are contained or catastrophic.
{% endhint %}

## Articles in this section

1. [3.1 What Even is an AI Sandbox?](/handbook/3.-runtime-sandbox-and-autonomy/3.1-what-even-is-an-ai-sandbox.md)
2. [3.2 Approval policies and least-privilege autonomy](/handbook/3.-runtime-sandbox-and-autonomy/3.2-approval-policies-and-least-privilege-autonomy.md)
3. [3.3 Network egress control](/handbook/3.-runtime-sandbox-and-autonomy/3.3-network-egress-control.md)
4. [3.4 Internet access and browser automation](/handbook/3.-runtime-sandbox-and-autonomy/3.4-internet-access-and-browser-automation.md)
5. [3.5 Computer Use / desktop control risks](/handbook/3.-runtime-sandbox-and-autonomy/3.5-computer-use-desktop-control-risks.md)
6. [3.6 Scheduled and background tasks](/handbook/3.-runtime-sandbox-and-autonomy/3.6-scheduled-and-background-tasks.md)
7. [3.7 Remote access, dispatch and SSH](/handbook/3.-runtime-sandbox-and-autonomy/3.7-remote-access-dispatch-and-ssh.md)
8. [3.8 File and filesystem access controls](/handbook/3.-runtime-sandbox-and-autonomy/3.8-file-and-filesystem-access-controls.md)
9. [3.9 Central hosted-agent runtime hardening](/handbook/3.-runtime-sandbox-and-autonomy/3.9-central-hosted-agent-runtime-hardening.md)

## Frequently asked questions

**What is the minimum safe runtime boundary for an agent?**\
Use the narrowest filesystem, network, credential, tool, duration, and action scope that supports the approved task. Separate the orchestrator from tool execution where feasible, require approval beyond the baseline, and test termination before production.

**Why do local and hosted execution need separate reviews?**\
They have different isolation, credential, data-retention, network, evidence, and incident-containment paths. A product setting may enable both without applying the same controls to both runtimes.

## Related handbook guidance

* [AI Security Handbook](/ai-security-handbook.md)
* [1.7 Human-in-the-loop and approval policies](/handbook/1.-identity-and-access/1.7-human-in-the-loop-and-approval-policies.md)
* [5.1 Prompt injection: the connective risk](/handbook/5.-threats-and-adversarial/5.1-prompt-injection-the-connective-risk.md)
* [6.2 OpenTelemetry for AI runtime visibility](/handbook/6.-observability-audit-and-evidence/6.2-opentelemetry-for-ai-runtime-visibility.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.harmonic.security/handbook/3.-runtime-sandbox-and-autonomy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.