CircleCI + Memtro

Only when you ask, and only what it has been granted: trigger a pipeline on a branch or tag (uses credits); rerun a workflow, or only its failed jobs (uses credits); cancel a running workflow or job; approve a job waiting on approval, such as a deploy; create, change or delete a scheduled pipeline; roll a deployed component back to an earlier version. 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 CircleCI records into memory as entities.

Personal API token. In app.circleci.com open User settings → Personal API Tokens → Create New Token. It acts as you, so it sees and runs every project you can. Set an expiry: CircleCI emails before it runs out.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with CircleCI for you. 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.