Interface StudioToolPolicyExperimental

The session's approval policy. Defaults approve the canonical HONUA_STUDIO_TOOL_FAMILY in every view and allowlist nothing — so an unclassified server (today's server, pending honua-server#3428) routes no composition tools until a consumer configures allowlist explicitly.

interface StudioToolPolicy {
    allowlist?: readonly string[];
    approve?: ((entry: StudioToolCatalogEntry) => boolean);
    families?: readonly string[];
    required?: readonly string[];
    views?: readonly string[];
}

Properties

allowlist?: readonly string[]

Exact tool names to route when the server supplied NO classification metadata for them. This is the honua-server#3428 fallback; it is matched by exact string equality and is never interpreted as a prefix or pattern.

[]
approve?: ((entry: StudioToolCatalogEntry) => boolean)

Final veto, applied only to entries family/view/allowlist already approved.

families?: readonly string[]

Server-owned families approved for routing.

[HONUA_STUDIO_TOOL_FAMILY]
required?: readonly string[]

Tool names this consumer depends on. Any that discovery does not end up routing is reported as a migration diagnostic instead of being silently dropped.

HONUA_STUDIO_MCP_TOOL_NAMES
views?: readonly string[]

Server-authored views approved for routing. When omitted, every view inside an approved family is approved. When supplied, a descriptor must declare a view from this list — an undeclared view is a rejection, not a pass.