McpApprovalsConfig
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/shell-policy.ts:592
EXT-70 §4.7/§9 — the approvals.mcp block: the per-server relationship, keyed by the user’s own
mcpServers config key.
defaults applies to servers NOT named under servers — §9’s own gloss. A server that names
itself states its own relationship in full, so {"jira": {}} trusts nothing however permissive
defaults is: trust by omission is exactly the failure §4.7.1 exists to prevent, and the fail-
closed direction is the one a silent config edit must fall in.
A key here is not validated against mcpServers. A user may write the policy before adding
the server, and coupling the two would make config ORDER matter.
This block cannot live inside mcpServers, which is modelled permissively because it carries
runtime objects.
Properties
Section titled “Properties”defaults?
Section titled “defaults?”
optionaldefaults?:McpServerApprovalsConfig
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/shell-policy.ts:594
The relationship with every server not named under servers.
servers?
Section titled “servers?”
optionalservers?:Record<string,McpServerApprovalsConfig>
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/shell-policy.ts:596
Per-server relationships, keyed by the user’s own mcpServers config key (§4.7.5).