Nomad + Memtro

Only when you ask, and only what it has been granted: dispatch an instance of a parameterized job; force a new run of a periodic job now; scale a job's task group to a new count; revert a job to an earlier version; re-evaluate a job, optionally rescheduling failed allocations now; stop a job, optionally purging it; stop an allocation so it is rescheduled; restart an allocation's tasks in place; send a signal to an allocation's tasks; drain a node, or stop draining it; mark a node eligible or ineligible for new work; promote a deployment's canaries; fail a deployment (rolls back to the last stable version); pause or resume a deployment. 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.

Address and ACL token, plus optional port and namespace. In Nomad, write an ACL policy with read-job, list-jobs and node read for the namespaces Memtro should see. Add write capabilities only for the actions you allow, then create a client token with it.