Axiom + Memtro

Only when you ask, and only what it has been granted: add an annotation to one or more datasets' charts; edit an annotation; delete an annotation (permanent); create a monitor that alerts named notifiers; change, disable or re-enable a monitor; delete a monitor (permanent); create a dataset; change a dataset's description or retention (shorter retention removes older data); trim a dataset's events older than a number of days (permanent); delete a dataset and all its data (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.

API token. In app.axiom.co open Settings → API tokens → New API token and choose Advanced permissions. A basic token can only ingest data, so it connects but cannot query.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Axiom, choosing the same kinds; the tab shows Axiom's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.