Audit your Claude Code configuration for security issues using AgentShield.
When to Activate
- Setting up a new Claude Code project
- After modifying
.claude/settings.json, CLAUDE.md, or MCP configs
- Before committing configuration changes
- When onboarding to a new repository with existing Claude Code configs
- Periodic security hygiene checks
What It Scans
Prerequisites
AgentShield must be installed:
Usage
Basic Scan
Auto-Fix
Apply safe fixes automatically (only fixes marked as auto-fixable):
This will:
- Replace hardcoded secrets with environment variable references
- Tighten wildcard permissions to scoped alternatives
- Never modify manual-only suggestions
Opus 4.6 Deep Analysis
Run the adversarial three-agent pipeline for deeper analysis:
This runs:
- Attacker (Red Team) — finds attack vectors
- Defender (Blue Team) — recommends hardening
- Auditor (Final Verdict) — synthesizes both perspectives
Initialize Secure Config
Scaffold a new secure .claude/ configuration from scratch:
Creates:
settings.json with scoped permissions and deny list
CLAUDE.md with security best practices
mcp.json placeholder
GitHub Action
Add to your CI pipeline:
Severity Levels
Interpreting Results
- Hardcoded API keys or tokens in config files
Bash(*) in the allow list (unrestricted shell access)
- Command injection in hooks via
${file} interpolation
- Shell-running MCP servers
High Findings (fix before production)
- Auto-run instructions in CLAUDE.md (prompt injection vector)
- Missing deny lists in permissions
- Agents with unnecessary Bash access
Medium Findings (recommended)
- Silent error suppression in hooks (
2>/dev/null, || true)
- Missing PreToolUse security hooks
npx -y auto-install in MCP server configs
Info Findings (awareness)
- Missing descriptions on MCP servers
- Prohibitive instructions correctly flagged as good practice
Security scanning should be part of your regular workflow. Run AgentShield before committing configuration changes.
Links