A team adds a Claude Code step to their CI pipeline that runs on every push to main. The step has access to the production database credentials (inherited from the CI environment). The step's task is to summarize what changed in the latest commit. What is the problem?
Answer: The production database credentials are in scope for the Claude Code step, creating unnecessary blast radius — the task only requires git access and the Anthropic API key
The task requires only git access and the Anthropic API key — nothing more. Having production database credentials inherited by the CI environment means those credentials are available to any tool Claude Code might call, including Bash commands that could accidentally or maliciously query or modify the database. This is unnecessary blast radius. The fix is to run the Claude Code step in an isolated environment with only the credentials it needs. Summarizing commits is a valid task (A). --read-only doesn't block all tools (B). CI steps can produce output in multiple ways (D).