authentik + Memtro

Only when you ask, and only what it has been granted: create a user; change a user's name, username or e-mail, or deactivate or reactivate them; delete a user; create a group; rename a group; delete a group; add a user to a group; remove a user from a group; create an application; change an application's name, launch URL, description, publisher, group, visibility or provider; delete an application; sign a user out of one session; create an invitation; e-mail an invitation link to people; delete an invitation; create a role; add a user to a role; remove a user from a role. 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.

Host and API token. In the admin interface create a service account for Memtro with a role holding view permissions on users, groups, applications and events, plus add, change or delete only if you want the actions.