Tool registry

Generated from the live registry at build time. It cannot describe a capability the gateway does not enforce.

The complete set of 28 tools an agent can call. Nothing callable exists outside this registry, and nothing in it is reachable except through the gateway.

#Every tool

#What the effect column means

none

An internal read. Nothing leaves the platform and nothing changes. Never gated.

external_read

Crosses the boundary and may disclose a patient to a payer, but asserts nothing and creates no obligation - an eligibility question leaves the payer's state identical. Not gated, because a human approving every lookup buys nothing and pushes the work back to the fax machine it replaced. Bounded and audited instead: the risk here is disclosure VOLUME, not any single call.

write

Changes something. If the something belongs to us it may be ungated; if it belongs to a practice - a chart - it is gated or explicitly bounded.

external

Asserts something to a payer. Always gated, at every autonomy level, with no exception and no configuration that removes it.

#Tools that always stop for a human

#Tools gated conditionally

A conditional gate is a function of the arguments and the practice's configuration, evaluated per call. It is not a default that a caller can pass a flag to skip.

#Rate-limited tools

An ungated tool that can flood something is bounded instead. Creating a task asks a human to act rather than acting, so gating it would mean a human approving the act of asking a human - but burying a worklist is its own harm, so it is capped.