OpenMetadata + Memtro

Only when you ask, and only what it has been granted: acknowledge a data quality incident; assign or reassign an incident to a user or team; resolve an incident with a reason and a comment; reopen a resolved incident; open a new incident on a test case; add a glossary term to a glossary; rewrite the description of a table or glossary term. 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 JWT token. In OpenMetadata, an administrator opens Settings, then Bots, gives a bot a role and generates a token. A personal access token also works. Edits need Data Steward rights.

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