sec-default mod
A guard for organizations: keeps managed hooks, managed CLAUDE.md, settings and deny rules out of reach of the mods a person installs.
Last checked against the official docs: 2026-10-02
| Type | Built into Claude Code |
|---|---|
| Name in /plugin | cc-plugin-sec-default |
| Source | anthropics/claude-code · mods/sec-default |
What it does
- Mods can hook almost every event, so a mod you install could in principle touch things your organization controls. sec-default sits in the outermost position and stops that.
- It protects the organization's settings hooks, managed instructions and rules, settings reads, MCP allowlist and deny rules. It adds no policy of its own; everything else passes through.
- If it cannot read the managed policy, it fails closed and treats the policy as in force.
How to get it
- Loads automatically on machines with managed settings and for Team or Enterprise organizations.
- Users cannot turn it off. An administrator controls its position through managed settings.
What you can learn from its code
If you are writing your own mod, this one is a good example of:
- Enforcing policy with a mod
- Refusing calls from user-installed mods
See how to create a mod to get started.
Related mods
- Blast Radius: Holds a risky shell command such as rm -rf or a force push and shows what it would change, with Proceed and Cancel buttons.
- Secret Redactor: Masks API keys, JWTs, private keys and connection strings in tool output before Claude sees them.
- Large Edit Confirmation: Asks you to confirm before a large Edit or Write. Without an interface to ask, it refuses.
- Protected Paths Guard: Protects files matching path patterns from Edit, Write and notebook changes.