Building a Local LLM · 29/30 · Advanced and Operations
Full series and learning sequence · Practice code ZIP
Running a model on a PC still leaves data and permission boundaries to review. Inspect API listen addresses, source text retained in logs, external tools and file access. Apply the checks to the configuration built in the series, and record how to stop or recover it.
Use a running private practice configuration. Check by writing down the network address, data location, and scope of access for the tool.
Receiving address and API access
Get-NetTCPConnection -State Listen | Where-Object {$_.LocalPort -in 11434,1234,18789,3000} | Select-Object LocalAddress,LocalPort,OwningProcess127.0.0.1 is the loopback for that environment and 0.0.0.0 means listen on any IPv4 interface. Divide the boundaries between Windows, WSL, and containers, and also check the Docker publishing port. We do not treat the local default Ollama like a shared service with user authentication.
When used by multiple people, authenticated proxies, access control, request size and concurrency limits, TLS, etc. must be designed. The procedure for exposing the raw inference API to the Internet by simply configuring port forwarding on the router is not included in this personal exercise.
Scope of application of OLLAMA_NO_CLOUD
Ollama’s cloud model and web search functionality can currently be controlled with the OLLAMA_NO_CLOUD setting in the FAQ. Below is an example of a Windows user environment variable. After applying, completely close the app and then restart it.
[Environment]::SetEnvironmentVariable("OLLAMA_NO_CLOUD", "1", "User")This setting does not block external connections from other apps. OpenRouter scripts and other Hermes providers, messenger and browser tools must be checked separately. In environments where external transmission is prohibited by policy, the OS network policy and connection history are also checked.
Original text, index, and backup location
| assets | What to check |
|---|---|
| Original text/index | Per-user read permissions, re-indexing after deletion |
| conversation/memory | Storage path, storage period, and deletion method |
| log | Original text/key included, access rights |
| API key | Dedicated key, limit, and disposal procedures |
| Model/Extension Package | Official sources, licenses, version history |
We do not treat embeddings as a result of anonymization of the original text. The example’s index.json also contains a snippet of the original text. Backups should be protected to the same standards as the original. When receiving models and plugins, we also check the sources of executable files and external code.
Tool Permissions and How to Stop
Distinguish between prompts to not follow instructions in the document and actual execution permissions. It is limited to tool whitelisting, argument checking, file permissions and quarantine, and approval steps. Separate reading and external sending permissions and do not connect any tools or messengers that are not required.
Also write down how to stop if something goes wrong. Make sure to stop the gateway, destroy the key, back up the settings and check the last good version. If you replace a model, tool, or extension, these checks will be run again.
reference material
Documentation and model tags checked: October 18, 2026. Primary lab environment: Windows 11 x64.
