Struct Registry 

pub struct Registry { /* private fields */ }

A catalog of tools that dispatches through the leash.

Each Registry::dispatch looks up the named tool, has a fresh Gate authorize it against the supplied grant (the single mint site), then runs it. A registry has no ambient authority of its own — all authority flows in per-dispatch as the granted caveats.

Implementations

impl Registry

pub fn builder() -> RegistryBuilder

Start building a registry with explicit tool registration.

pub fn tool_definitions(&self) -> Vec<Value>

The MCP tools/list payload: one object per tool with name, description-free inputSchema. (Descriptions are a frontend concern.)

pub fn tool_names(&self) -> Vec<&str>

The set of registered tool names (sorted). Used by the CI presence test.

pub fn contains(&self, name: &str) -> bool

Whether a tool is registered under name.

pub async fn dispatch( &self, name: &str, args: Value, granted: &Caveats, ) -> Result<Value, ToolError>

Dispatch name with args, enforced by the leash.

A fresh gate (seeded with the grant’s max_calls and the registry’s generation) authorizes the tool, minting the crate::ToolContext the tool needs. If authorization is denied, the tool never runs.

pub async fn dispatch_with_strength_floor( &self, name: &str, args: Value, granted: &Caveats, strength_floor: AxisEnforcement, ) -> Result<Value, ToolError>

Dispatch name with an explicit minimum confinement strength.

This is the strong-principal form of Self::dispatch. The selected floor is stamped into the unforgeable crate::ToolContext at the gate’s mint site and follows delegated trusted-worker requests. A subprocess boundary then refuses to launch if any restricted axis would fall below that floor. This closes the gap between a host’s prospective enforcement check and the backend actually governing execution.

The ordinary Self::dispatch remains backwards-compatible and uses the default AxisEnforcement::Advisory floor.