Automated Directory Auditing
Audit Your Entire Codebase Offline
AI Summary / Key Takeaways
"Prevent catastrophic supply chain leaks. Connect the MCP Server to audit entire local directories for hardcoded secrets, JWTs, and PII. Ensure your repository is completely clean before engaging with autonomous agentic workflows. Available via the MCP Server."
Enterprise-Grade AI Privacy
Add custom redaction rules and priority support with PRO.
The Challenge with AI Data Workflows
Developers routinely hardcode API keys or production database credentials during testing and accidentally commit them to GitHub. Existing secret scanners often send code telemetry back to cloud vendors, violating air-gapped security policies.
How It Works
Initialize MCP Server
Connect the PrivacyScrubber MCP Server to your IDE. It runs completely offline.
Trigger the Audit
Instruct your AI agent to run the 'audit_directory_for_pii' tool against your current working directory.
Review the Report
The tool generates a comprehensive list of flagged files, exact line numbers, and entity types (e.g., AWS Key, Email). You can then instruct the AI to call 'sanitize_file' on the flagged items.
What Teams Achieve with Local PII Masking
Swipe to read more
Supported Formats & Limitations
Supported Formats
System Limitations
- Excludes binary files (images, compiled objects) by default
- Scans are bounded by OS file-read constraints and local memory limits
- Heuristics optimized for code, so prose-heavy documentation may yield false positives for specific variables
Securing the Autonomous Dev Workflow
As developers shift from simple code completion to autonomous multi-agent workflows, the surface area for data leakage expands exponentially. The audit_directory_for_pii tool provides a critical 'pre-flight check' for any AI agent, ensuring that your enterprise intellectual property and customer data are mathematically scrubbed before any network request is made.
Feature Reliability & Audit
This enterprise feature is powered by our Local-First Sanitization Engine. Unlike legacy cloud DLP tools, PrivacyScrubber processes your Automated Directory Auditing logic 100% within your browser's V8 sandbox. This architectural decision ensures that even the most complex detection patterns never expose raw data to an external API.
Airplane Mode
Verified feature operational integrity without network connectivity.
Step-by-Step Guide
How to use this feature
Ask the AI Agent
Prompt your AI: 'Run a security audit on this directory using the PrivacyScrubber MCP server.'
Agent Executes Tool
The agent autonomously calls audit_directory_for_pii, parsing your entire file tree locally.
Agent Plans Fixes
Based on the audit report, the agent can autonomously propose code changes or call sanitize_file to redact the hardcoded secrets.
Commit Securely
Your codebase is now clean of PII and secrets, preventing leakage into the AI's training data stream.
Frequently Asked Questions
How fast is the directory audit?
The audit tool is heavily optimized using asynchronous I/O and worker threads in Node.js. It can scan a 10,000-file repository in under 4 seconds.
Does it upload my code anywhere?
No. The MCP server runs as a local process on your machine. The audit tool reads files locally and returns the report directly to the IDE's agent context. Zero data is transmitted to our servers.
Protect Your Team's AI Prompts in Under 30 Seconds
Protect My TeamNo server uploads. Works 100% offline in browser RAM.
