summary: Which Claude Code built-in tools are globally denied (Workflow, Artifact, SendUserFile, ReportFindings) and why, where the deny lives (~/.claude/settings.json permissions.deny), measured per-schema token costs, and which tools are deliberately kept.
"SendUserFile", "ReportFindings"]}`. This removes their schemas from every session's
context (~6.5k tokens/session saved), identical in effect to `--disallowedTools`
(measured 22,532 vs 22,536). Settings-file deny was chosen over a `cyolo`-alias flag
so it covers ALL entry points (headless scripts, IDE sessions, anything shelling out
to `claude`), not just alias-launched sessions.
**If a session ever "can't find" one of these tools, this deny list is why.**
Revert = delete that one line from `~/.claude/settings.json`.
## Denied tools — what they are and why they're safe to drop
Ground truth: `tool_use` counts across all `~/.claude/projects/**/*.jsonl`
transcripts, 2026-06-01→2026-07-08 (~17k total tool calls).
| Tool | What it is | Lifetime calls | Schema cost |
|---|---|---|---|
| Workflow | JS-scripted multi-agent fan-out orchestration ("ultracode"-style) | 0 | **~5,982 tokens** — the single largest schema, ≈ the entire system-prompt text |
| Artifact | Standalone artifact/document generation | 0 | ~527 combined for these three |
| SendUserFile | Push a file to the user in supported UIs | 0 | ↑ |