ACB-CFG-005: Tool server tools are pre-approved by name, never server-wide

FieldValue
Statusdraft
Severitymedium
Check typestatic
Applies toagent-settings, managed-settings
Profilesstrict-general
Exceptionspermitted

Description

An allow rule in the agent's committed permission configuration that pre-approves a tool server's tools names one tool exactly. No allow rule approves every tool a server offers, or every tool whose name matches a pattern.

Rationale

A reviewer who approves a tool server approves the tools it offered at that moment. A server-wide or pattern allow rule also approves every tool the server adds later, so a server whose package, endpoint or operator is compromised after review can introduce a tool that runs without anyone being asked. Naming each tool keeps a new tool behind the host's approval prompt and turns widening the approval into a reviewed change to the settings file. An exact-name rule still matches a tool whose description or behaviour changes after review, so this control does not cover redefinition of an approved tool.

Audit procedures

tools-allowed-by-name (structure)

Collect the allow rules from every agent settings file in the repository. No allow rule matches a form the client defines as approving more than one named tool of a tool server: a rule naming only the server, or a rule with a wildcard in the tool name. Not evaluated when the client defines no such forms.

Illustrative failing indicators (non-exhaustive):

Remediation

Replace each server-wide or pattern allow rule with one rule per tool the agent needs without a prompt, and leave every other tool of the server to the host's approval prompt.

Implementation notes

Client-specific facts from clients/; the control above is the requirement.

claude-code: tools-allowed-by-name

MCP tools are named `mcp__<server>__<tool>`. As an allow rule, `mcp__<server>` and `mcp__<server>__*` match every tool of the server, and a glob after the `mcp__<server>__` prefix, such as `mcp__github__get_*`, matches every tool whose name fits it. Unanchored allow globs such as `mcp__*` are skipped and approve nothing. Allow rules in a project's `.claude/settings.json` apply only after the workspace trust dialog, which lists them, is accepted.

References