CoursesClaude Code in Practice
Permissions, Hooks and MCP
The settings that hold whatever Claude decides: permission rules and the file they live in, hooks that block or format at a fixed point, MCP servers at the right scope with the token out of the file, and the -p runs where nobody is watching.
- Lessons
- 6
- Exercises
- 34
- Minutes
- 38
- 1
Permission Rules
After this lesson you can put an allow, deny or ask rule in the right settings file, say which file wins when two disagree, and fix a rule that does not load.
DebugMultiple choice - 2
Hooks
After this lesson you can write a hook that runs on a fixed event, block a tool call before it happens, and say when a rule belongs in a hook rather than in CLAUDE.md.
DebugFill blankMultiple choiceTrace - 3
MCP Config
After this lesson you can add an MCP server at the right scope, keep its token out of the committed file, and size a server the team shares the way you size any tool list.
DebugFill blankMultiple choice - 4
Headless Runs
After this lesson you can put Claude Code in a script or a CI step, say what -p changes about prompts and MCP approval, and put the boundary where it still holds when nobody is watching.
DebugMultiple choiceTrace - 5
Checkpoint: Rules and HooksCheckpoint
Permission files, hooks, MCP scopes and unattended runs in fresh situations.
DebugFill blankMultiple choice - 6
Boss: Lock Down the Team SetupBoss
Noor joins the six-person billing-api team as an intern. The repo holds scripts/deploy-prod.sh and a .env of live keys. Sam asks you to make sure no Claude Code session reaches production without a person, without slowing the other five: deny rules, a hook on the deploy script, a scoped .mcp.json, and a check that holds when nobody is watching.
DebugFill blankMultiple choiceTrace