Security audit
Security checks for vulnerabilities and agentic risk
The MailGenius workflow is reasonable, but its setup can execute unverified code and introduce broader changes to your agents without clearly explaining them.
Review and approve CLI installation separately, using a verified release. OOMOL intermediates your MailGenius account access. If you only want MailGenius operations, disable startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI environment settings](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). The downloaded installers and hosted connector were not verified; the review concerns are setup control and under-disclosed agent changes.
The supplied command executes an external installer, with no visible connection to MailGenius or its data operations. Nothing in the provided content establishes this installation as a supporting dependency for the declared purpose. The remote script's contents are not supplied, so its further effects cannot be assessed.
The command pipes a mutable remote installer directly into Bash without a pinned version, signature check, or independently verified digest; the PowerShell alternative has the same trust issue. Compromise of the installer distribution path could execute attacker-controlled code with the invoking user's privileges, although the documented prerequisite context provides no evidence of deliberate malicious intent.
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 fallback directs installation through remote scripts without explaining that they execute local code and may modify the system, or requiring explicit installation approval. Although setup runs only when the CLI is missing, an ordinary MailGenius request can therefore lead to local code execution beyond the user's requested service operation.
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