Grist + Memtro

Only when you ask, and only what it has been granted: add rows to a table; change values in existing rows; delete rows from a table; add or update rows matched on chosen columns (upsert); add a table, add columns, rename a table, or delete a column with its data; create a document in a workspace, copy one, rename it, or move it to another workspace; move a document to the trash or restore it from there; create a workspace. 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 Grist open your profile picture → Account settings → Developer → API Key, click Create and copy it. The key carries all of its account's access with no scopes, so consider a dedicated user shared into only the right documents.

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