Zenduty + Memtro

Only when you ask, and only what it has been granted: create an incident (pages the service's on-call); acknowledge, resolve, reassign or edit an incident; add a note to an incident; edit an incident note; delete an incident note; tag an incident; remove a tag from an incident; add a responder to an incident (pages them); create a maintenance window that silences a team's services; delete a maintenance window; override who is on call on a schedule for a period; invite a user to the account and a team (emails them); remove a user from the account. 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 Zenduty, open the profile bubble, then Account, then API Keys, and create a key. Only the Account Owner or an Account Admin can, and the key acts as its creator. Copy it, as it is shown once.

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