Security audit
Security checks for vulnerabilities and agentic risk
The mail controls are sensible, but setup directs the agent to execute an unverified online installer without separate user approval.
Review and install the CLI separately before allowing mail tasks to trigger setup. Understand that OOMOL handles the connected account, and retain confirmation for sending, changing, moving, or deleting mail. The remote installer and hosted connector were not bundled for inspection; the Review verdict concerns setup control, not demonstrated malicious behavior.
The supplied chunk performs remote script execution rather than any demonstrated NetEase Mail operation. Although installing a dependency could be a supporting implementation detail, nothing supplied establishes this installer as a dependency for the declared mail functionality. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping a mutable HTTPS installer directly into bash executes remote code without version pinning or independent integrity verification; the PowerShell example has the same weakness. Compromise of the distribution endpoint could yield arbitrary execution with the invoking user's privileges, potentially exposing local files and credentials, although the conditional setup path and declared oo-only tool restriction limit immediate reachability.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The missing-CLI fallback directs installation through remotely downloaded shell or PowerShell code without explaining local changes or requiring explicit installation approval. Although this runs only after a missing-command error, a mail-management request should not implicitly authorize executing installation code on the user's machine.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources