Python: .NET: Python: clarify CodeAct guest packages and host network access

dotnet/src/Microsoft.Agents.AI.Hyperlight/README.md

@@ -35,6 +35,24 @@ Both surfaces support:
   the meantime.
 * A Hyperlight Python guest module when using `SandboxBackend.Wasm`.
 
+## Network access and guest packages
+
+`HyperlightCodeActProviderOptions.AllowedDomains` controls outbound requests
+from the sandbox. It does not install guest packages or expose host-installed
+dependencies to guest code.
+
+`CreateForWasm(modulePath)` selects an existing `.wasm` or `.aot` guest module;
+it does not build a guest or install Python packages. The Agent Framework
+integration does not provide a custom guest build or package installation
+workflow. Package availability depends on the selected module and backend;
+the default JavaScript backend does not run Python code.
+
+For operations requiring application dependencies or external APIs, register
+an `AIFunction` in `Tools` and invoke it from the guest with `call_tool(...)`.
+Keep credentials and authorization in the host function. These functions run
+outside the guest, so `AllowedDomains` does not restrict their network requests;
+enforce any required destination policy in the host function.
+
 ## Status
 
 Preview. API may change until the underlying Hyperlight SDK reaches a stable

python/packages/hyperlight/README.md

@@ -186,6 +186,24 @@ Nested output paths require secure directory-relative file opening. On platforms
 without that capability, nested attachments fail closed; write attachment files
 directly under `/output` for portable behavior.
 
+## Network access and Python packages
+
+`allowed_domains` controls outbound requests from the sandbox. It does not
+install Python packages or make packages from the host environment available
+inside the guest. Installing a dependency with `pip` on the host is separate
+from making it importable in sandboxed code.
+
+`module_path` selects an existing guest module; it is not a package-installation
+option. The Agent Framework integration does not provide a custom guest build
+or package installation workflow. Guest package availability depends on the
+selected Hyperlight module and backend.
+
+For operations requiring host-installed libraries or external APIs, register a
+host function in `tools` and call it from sandboxed code using `call_tool(...)`.
+Keep credentials and access checks in that function. Host tools execute outside
+the guest, so the sandbox's `allowed_domains` setting does not restrict their
+network requests; enforce any required destination policy in the host tool.
+
 ## Notes
 
 - This package is intentionally separate from `agent-framework-core` so CodeAct

python/packages/monty/README.md

@@ -198,6 +198,20 @@ Available primitives:
 | `asyncio.gather(...)` | Fans out concurrent tool calls. |
 | `print(...)` | Captured and surfaced as text in the tool result. |
 
+## Network access and Python packages
+
+Monty runs its own Python interpreter, not the host's Python environment. This
+integration exposes no `pip` or package-installation option; installing a
+dependency on the host does not make it importable in Monty code. Use the
+interpreter's supported modules for code that runs inside Monty.
+
+Unlike Hyperlight, `MontyCodeActProvider` and `MontyExecuteCodeTool` do not expose
+an `allowed_domains` option. For external API calls or operations requiring
+host-installed packages, register a host function in `tools` and invoke it with
+`await tool_name(...)` or `await call_tool("name", ...)`. Keep credentials,
+authorization, and any destination allow-list checks inside that function.
+These functions execute on the host rather than inside the Monty interpreter.
+
 ## Notes
 
 - `MontyCodeActProvider` and `MontyExecuteCodeTool` mirror the API surface of