Rollbar + Memtro

Only when you ask, and only what it has been granted: resolve, mute or reactivate an item; assign an item to a user or team, or unassign it; snooze or unsnooze an item; change an item's title or level; comment on an item; record a deploy of a revision to an environment; delete one occurrence (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 Rollbar records into memory as entities.

Project access token. In Rollbar open the project → Settings → Project Access Tokens → Create a new access token with the read scope, plus write for changing an item's status, assignee, snooze, title or level, commenting or deleting an occurrence, and post_server_item only for recording a deploy.

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