Tool registry
Read-only. Manifests are git-driven and CI-validated. Only published versions reach the agent.
config/upstreams.yaml · 0 configured
| Upstream | Destination | Auth | State | |
|---|---|---|---|---|
| Loading… | ||||
tools/registry/*.yaml · 0 live · 0 unpublished
| Tool | Status | Risk tier | Description | |
|---|---|---|---|---|
| Loading… | ||||
What the viewer must surface
upstream— the name of an application configured inconfig/upstreams.yaml— plus theendpointsmap keyed by that name. The gateway front-ends any backend, so several endpoints per tool is normal: it is how one manifest targets a different application per workspace, or spans a migration cutover, without being rewritten.- Path-parameter constraints: every
{param}must declareformat: uuid,integer, or an anchoredpattern, and CI fails unconstrained ones (S2). An unconstrained param turns an approvedwriteinto a privileged mutation that is still schema-valid and hash-matching. - Risk tier and manifest digest — the digest is re-compared immediately before execution (S13).