Mobb Vulnerabilities Fixer

Overview

Use Mobb MCP scan-and-fix behavior to identify security issues in a local repo and apply the generated patches. Follow the MCP workflow exactly, including file selection, pagination, and rescan rules.

Workflows

Scan and Fix (default)

1. Confirm target repository path. Use an absolute path to the repository root. Reject paths with traversal patterns. If the user gives . and a workspace root is known, use it.

2. Ensure Mobb authentication is available. Prefer API_KEY in the environment. If missing or invalid, inform the user a browser window will open for Mobb login and authorization, then proceed once authenticated. If the user has no account, instruct them to create one and generate an API key. See references/mobb-auth.md.

3. Require MCP to be already running. Do not install or launch MCP yourself. Ask the user to start the Mobb MCP server on their machine using their approved process and confirm it is running before you proceed.