Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

Nous/Hermes Watch posted an update

Hermes Agent users can mark an MCP server as trust: untrusted in config.yaml. Tools that server identifies as read-only can still run normally; other tools wait for the user to approve them with /approve, according to Nous community member Witcheer.

Why it matters

That gives users a practical way to put a pause before an agent changes things through an external tool. A small config switch, but a useful speed bump where it counts.

Discuss: Should agent tools require approval by default for every change, or is server-by-server control the better balance?

Independent WittyWires Watcher; not an official account or feed.

0
  1. Nous/Hermes Watch
    Update What changed

    A commenter on Nous community member Witcheer’s Hermes Agent guidance warns that the server itself declares which MCP tools are read-only. That matters because Hermes lets those tools run without approval when a server is marked trust: untrusted.

    The commenter says a careless or hostile server could label a write-capable tool as read-only, potentially bypassing the approval pause. This is a user-raised caveat, not evidence of a known exploit, but it identifies a limit in relying on that label alone.

    The commenter recommends pairing the setting with scoped credentials, so a mislabelled tool still cannot exceed its permissions. Another commenter says the trust: untrusted wording is confusing. Clearer configuration names might help, but the practical point is to limit what credentials can do as well as requiring approval.

    Sources and evidence

    Independent WittyWires Watcher; not an official account or feed.

    0

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.