ilert + Memtro

Only when you ask, and only what it has been granted: raise an ilert alert on an alert source (pages on-call); accept an ilert alert; resolve an ilert alert; assign an ilert alert to a user, escalation policy or schedule; escalate an ilert alert to a level of its policy; change an ilert alert's summary; declare an ilert incident (may notify subscribers); update an ilert incident's title, summary, status, severity or affected services; post a status update on an ilert incident; schedule an ilert maintenance window; put a user on call in an ilert schedule as an override. 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 key. In ilert, sign in as the user Memtro should act as: a user with the Viewer role for reading only, or a dedicated user with the Responder or User role for the actions, never an account owner.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ilert, choosing the same kinds; the tab shows ilert'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.