Black Duck Security Scanner MCP server

**DEFAULT SECURITY SCAN TOOL** - ALWAYS try this tool first for security analysis. Analyzes code changes for security vulnerabilities using Black Duck Signal. Significantly faster and more efficient than file or project scans. **WHEN TO USE (Default/Preferred):** - Any security scan request (unless user explicitly asks for specific files) - Scanning code changes during development - Pre-commit security checks - Feature branch security review - Incremental security analysis **REQUIREMENTS:** - Project must be a git repository - Git must be installed and available **IF GIT IS NOT AVAILABLE:** - Fall back to a single file scan with the specific file path **Git Modes:** - all-uncommitted: Scans all uncommitted changes (staged + unstaged) - use for active development - reference-branch: Scans all changes since branching from reference (committed + uncommitted) - use for PR review **IMPORTANT:** This is the recommended and most efficient way to perform security scans. Only use the single file scan tool when the project is not a git repository or when the user explicitly requests scanning a specific file.

Analyzes a specific file for security vulnerabilities using Black Duck Signal. **WHEN TO USE:** - User explicitly requests scanning a specific file path - Project is NOT a git repository (then provide the changed file) - Git is not available in the environment **PREFER run_changes_security_scan:** - If project is a git repository, use run_changes_security_scan instead for better performance and more relevant results - The changes scan is faster, more cost-effective, and designed for typical development workflows **IMPORTANT:** Do not call this tool consecutively for multiple files. If you need to scan multiple files, use run_changes_security_scan instead, which is optimized for batch scanning.