GaugeMesh
io.github.aliengineering-byte/gaugemesh
Route MCP capabilities through deterministic identity, policy, budget, and deadline constraints.
Install surfaces
How GaugeMesh runs, per the official MCP registry entry.
- oci
ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189
Governed execution
How KLA gates calls to GaugeMesh once it is connected.
A published policy defines which GaugeMesh actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agents and model providers you already run. See integrations.