Rootly + Memtro

Only when you ask, and only what it has been granted: add an internal event to an incident's timeline; add an action item to an incident; declare an incident (your Rootly workflows may page responders and open a channel); update an incident's title, summary, status, severity, services, environments or teams; mark an incident mitigated; resolve an incident; cancel an incident; delete an incident (permanent); assign an incident role to a user; subscribe users to an incident's updates; acknowledge an alert (stops its escalation); resolve an alert; snooze an alert for some minutes; escalate an alert (pages the next on-call level); update an action item's summary, status, priority, due date or assignee. 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 Rootly records into memory as entities.

API key. In Rootly open the Organization dropdown → Organization Settings → API Keys and Generate New API Key.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Rootly for you. 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.