LibreNMS + Memtro

Only when you ask, and only what it has been granted: add an entry to a device's event log; put a device into maintenance for a time window (silences its alerts); acknowledge a firing alert with a note (stops its notifications); un-acknowledge an alert so its notifications resume; add a device to monitoring; change a device's notes, purpose, display name, location, or disabled, ignored or notification settings; rename a device; queue a rediscovery of a device; delete a device and all its history (permanent); create an alert rule; edit, enable or disable an alert rule, or change who it notifies; delete an alert rule (permanent); add a service check to a device; change, ignore or disable a service check; delete a service check (permanent); create a device group; rename or change a device group's members or rule; delete a device group (permanent); set the notes on a device port. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Host and API token. In LibreNMS open Settings → API Settings → API Access and create an API access token for a dedicated user. The token acts with all of its user's rights, so give that user read access to the right devices, and only the rights for the actions an administrator will grant.