Logz.io + Memtro

Only when you ask, and only what it has been granted: enable an alert; disable an alert; create a log alert that notifies the recipients you name; delete an alert (permanent); add a deployment marker; add a value to a lookup list; remove a value from a lookup list (permanent). 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. An hourly sync anchors recently changed Logz.io records into memory as entities.

API token. In Logz.io, sign in to the account Memtro should read and open Settings → Tools → Manage tokens → API tokens. Create a token, which can do anything the account can.