What problem does it solve?
It reduces the risk of secret leaks, prompt-injection abuse, and unsafe tool or hook behavior in Gemini CLI projects by auditing your local configuration before deployment.
Core Features & Use Cases
- Configuration security audit for Gemini CLI: Detects hardcoded secrets, dangerous auto-run instructions, and prompt-injection patterns in GEMINI.md and related config files.
- Risk scanning across common attack surfaces: Reviews settings.json permissions/allow-lists, MCP server definitions, and hooks/agent files for command injection and overly broad tool access.
- Actionable, automatable hardening: Produces severity-graded reports and can apply safe auto-fixes (e.g., replacing hardcoded secrets with environment references and tightening wildcard permissions).
Use case: Before committing a new or updated .gemini/ setup, run this scan to catch critical issues like hardcoded tokens, unsafe shell access (e.g., Bash allow-list entries), and hook interpolation that could enable command injection.
Quick Start
Run a security audit of your repository’s Gemini CLI configuration by telling the agent: scan the current project’s .gemini/ directory for vulnerabilities and misconfigurations.