DeclaredToolAnnotationLookup
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/annotations.ts:76
Where declared annotations come from, split by the provenance that decides their trust.
Both members are optional and both may return undefined for a tool they do not know, which
yields the fail-closed defaults — never “trusted, declaring nothing”. An absent lookup is
therefore the safe configuration rather than a broken one, and a source built with neither member
is exactly the constant fail-closed source.
Properties
Section titled “Properties”builtIn?
Section titled “builtIn?”
optionalbuiltIn?: (name) =>DeclaredToolAnnotations|undefined
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/annotations.ts:81
Our own tools, by tool name. Whatever this returns is trusted verbatim — no per-hint filter applies, because we (or the user, in their own config) authored it.
Parameters
Section titled “Parameters”string
Returns
Section titled “Returns”DeclaredToolAnnotations | undefined
optionalmcp?: (server,name) =>DeclaredToolAnnotations|undefined
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/annotations.ts:87
One MCP server’s declaration for one tool, from its tools/list response. server is the
user’s own mcpServers config key (§4.7.5), which is also the key its trust is looked up
under; nothing a server says about its own name ever participates.
Parameters
Section titled “Parameters”server
Section titled “server”string
string
Returns
Section titled “Returns”DeclaredToolAnnotations | undefined