You want full speed.
Not a deleted home directory.
--dangerously-skip-permissions makes Claude Code a surgical instrument or a wrecking ball. The problem:
nothing between "100 permission prompts per hour" and "no guardrails at all."
Certiv is that middle ground.
Every Claude Code power user faces the same impossible choice
Neither works. Certiv removes the dilemma.
Without --dangerously-skip-permissions
- CLI tools blocked by constant permission prompts
- Production environments need autonomous operation
- You rubber-stamp approvals without reading
- Autonomous runs constantly interrupted
- CI/CD pipelines broken by prompt pauses
With --dangerously-skip-permissions
- Zero friction, but zero guardrails
- rm -rf ~/ can delete your entire home dir
- No logging of what Claude actually did
- Prompt injection acts with root authority
- Repo config can RCE before you approve
- API keys exfiltrated silently
- All actions auto-approved
- No visibility into what ran
- No rollback awareness
- Prompt injection executes freely
- Repo config can hijack session
- Safe actions auto-approved instantly
- Dangerous actions blocked pre-execution
- Full audit trail of every command
- Injections caught before they run
- Repo config scanned before session starts
Documented incidents. Real developers. Real damage.
From the Claude Code community, 2025–2026.
The home directory wipe
CC was asked to clean a repo. It generated rm -rf tests/ patches/ plan/ ~/. That trailing ~/ wiped the home directory: Desktop, Keychain, app data. Gone.
r/ClaudeAI incident · December 2025Firmware project → system wipe
Mike Wolak watched Claude execute rm -rf / on Ubuntu/WSL2. Logs: thousands of "Permission denied" for /bin, /boot, /etc. Every user-owned file gone. Never appeared in the conversation.
GitHub issue #10077 · Anthropic tagged area:securityRepo clone → instant RCE
Cloning a malicious repo and launching Claude Code triggers arbitrary shell commands via Hooks. Before the trust prompt. No interaction required.
CVE-2025-59536 · CVSS 8.7 · Check Point Research 2026API key theft on open
ANTHROPIC_BASE_URL in a repo config redirects API traffic to attacker infrastructure before the trust dialog. Active API key exfiltrated silently.
CVE-2026-21852 · Anthropic advisory · no interaction neededLive on camera: Claude Cowork deletes 11GB
James McAulay benchmarked folder organisation with instructions to retain user data. Cowork ran rm -rf, deleting ~11GB. Task list: "Delete user data folder: Completed." Posted on X. Everything gone. Live.
X (Twitter) · James McAulay · January 20266 attack surfaces Claude Code opens up
Documented, recurring patterns affecting teams deploying Claude Code at scale.
Repo config injection (RCE)
A malicious .claude/settings.json executes shell commands when a developer opens the project. One insider poisons the config; every teammate gets hit.
CVE-2025-59536 · CVSS 8.7API key exfiltration
Project configs redirect Claude's API traffic to attacker servers before the trust prompt. One stolen key accesses your entire workspace.
CVE-2026-21852 · no user interactionIndirect prompt injection
1pt white-on-white text in a .docx manipulates CC into uploading files to an attacker via the Anthropic API. Demonstrated by PromptArmor, January 2026. No special permissions.
OWASP LLM Top 10 · in-the-wildMCP trust boundary abuse
enableAllProjectMcpServers: true is a consent bypass. Any contributor can inject an MCP server that silently acquires filesystem, database, or Slack access. No approval dialog.
High severity · widely deployedScope creep & destructive drift
Without malicious input, CC "helps" by modifying files outside scope: removing system config, rewriting CI pipelines, deleting test directories. No injection required. Just AI helpfulness.
Permission noise → rubber-stampingCI/CD pipeline poisoning
CC modifying CI scripts can change build steps to exfiltrate artifacts and introduce auth bypasses. Changes scatter across files, framed as "cleanup," slipping through PR reviews.
Supply chain · enterprise-criticalThree policy layers. Pre-execution. Every time.
Certiv intercepts before execution. Not a log you read after the damage.
Hard rules, zero LLM in the loop
Enforced in microseconds. No LLM means no prompt injection.
- Block rm -rf ~/ and rm -rf / variants
- Deny ANTHROPIC_BASE_URL env overrides
- Block MCP auto-approval in untrusted repos
- Prevent writes to ~/.ssh, ~/.aws
- Enforce tool allowlists in bypass mode
Pattern-aware content scanning
Catches obfuscated attacks and hidden-text injection that regex misses.
- Scan docs for hidden prompt injection
- Detect credential aggregation patterns
- Flag outbound data exfil signatures
- Audit repo config before session start
- Catch scope creep before execution
Divergence detection
Compares your intent to Claude's next action. Blocks divergence. Escalates when it matters.
- Task scope vs. action scope diff
- Privilege escalation detection
- Git operation audit (commit hygiene)
- Human approval for CI/CD file edits
- Lineage trail: intent → execution
What Certiv actually does in practice
What gets blocked, escalated, and what runs free.
Home directory deletion - rm -rf ~/
Deterministic BlockedMalicious repo config - API redirect + RCE
Deterministic BlockedHidden prompt injection in .docx
Semantic BlockedCI/CD pipeline edit during refactor
Intent-based EscalatedLegitimate full-speed autonomous refactor
All layers PassedComplete audit trail: every command, every session
Full intent lineage from your prompt to every action CC took.
Ship at full speed.
Keep your home directory.
Smart Claude Code developers ship with guardrails.