Prefect + Memtro

Only when you ask, and only what it has been granted: run a deployment (schedules a flow run on your infrastructure); cancel a flow run; create a variable; update a variable's value or tags; delete a variable; pause a deployment's schedule (deletes its waiting scheduled runs); resume a deployment's schedule (schedules runs immediately); delete a deployment; delete a flow; retry a failed or crashed flow run (runs it again on your infrastructure); resume a paused flow run; rename or retag a flow run; delete a flow run and its logs; update a deployment's description, version, tags, parameters, work pool or queue, or concurrency limit; add a schedule to a deployment; change, activate or deactivate a deployment schedule; delete a deployment schedule; pause or unpause a work pool, or change its description or concurrency limit; create a work pool; create a work queue in a work pool; create a global concurrency limit; publish a markdown artifact; turn an automation on or off. 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 an API key or auth string. Self-hosted servers must be Prefect 3 over https. Prefect Cloud service accounts need a Pro or Enterprise plan. On Cloud open Account menu → API keys → +, as a dedicated user with only the workspace role it needs for what Memtro may run and change.