JFrog Artifactory + Memtro

Only when you ask, and only what it has been granted: set properties on an artifact or folder; remove properties from an artifact or folder; copy an artifact or folder to another repository path (overwrites what is there); move an artifact or folder to another repository path; delete an artifact or folder; promote a build: change its status and copy or move its artifacts to a target repository. 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.

JFrog Platform host and Access token. In the JFrog Platform, open Administration → User Management → Access Tokens → Generate Token, or generate an Identity Token from your profile to act as you.

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