Security audit
Security checks for vulnerabilities and agentic risk
The data-reading workflow fits its purpose, but setup directs your agent to execute an unverified downloaded installer without a separate approval step.
Prefer a reviewed, preinstalled CLI and require approval before running downloaded installers. Review its automatic skill synchronization and disable it if unwanted. Triple Whale requests and returned business/customer data pass through OOMOL. The installer contents and hosted connector implementation remain unverified.
The supplied chunk performs remote script execution rather than searching or reading Triple Whale data. It shows no Triple Whale interaction or connection establishing this installer as a supporting dependency. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
Piping a remotely fetched installer directly into bash executes mutable network content without an independent integrity check; the PowerShell alternative has the same issue. If the distribution endpoint or delivery chain is compromised, attacker-controlled code could run with the agent's local privileges and access files or credentials, although the missing-CLI condition and any enforced oo-only tool restriction limit 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 fallback directs the agent to install software after a missing-command error without explicitly obtaining approval for local changes or explaining that downloaded code will execute. Restricting installation to first-time setup reduces exposure, but a data-reading request does not itself authorize local software installation; the declared oo-only tool allowance may prevent execution if strictly enforced.
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