After Hermes Agent binds API Server to 0.0.0.0, the security risk increases significantly. The official API Server documentation warns that this interface gives full tool permissions, including terminal commands. If you want to make it network-accessible, you must at least have a API_SERVER_KEY and narrow the API_SERVER_CORS_ORIGINS.
Why is this dangerous?
Because Hermes Agent's API is not a "pure chat box", it can adjust terminals, files, and web tools. After being exposed, a loose configuration may become a remote command entry.
A more stable approach
- Continue to use
127.0.0.1by default. - Remote access is indeed required, plus reverse proxying, authentication, and minimized whitelisting.
- Don't be fooled into thinking that you must open the
0.0.0.0just because of Open WebUI or front-end access.
In a word: if you can not open the public network, don't open it; Once exposed, the Hermes Agent API is much more risky than a normal chat interface.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.