Security audit
Security checks for vulnerabilities and agentic risk
The Metabase workflow includes approval safeguards, but missing software triggers instructions to run an unchecked remote installer without separate user approval.
Review and install a pinned, verified CLI release yourself before enabling this skill. Decide whether to allow the CLI's automatic skill synchronization; its documentation provides OO_SKILLS_SYNC_DISABLED=1 to disable it. Use a narrowly scoped Metabase API key, trust OOMOL with the connected account, and retain explicit approval for writes and SQL execution. The remote installer and hosted connector were not verified.
The visible command executes an Oomol-hosted installer rather than interacting with Metabase. Nothing in the supplied chunk establishes that this installer is a supporting dependency for the declared functionality. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping the remote installer directly into bash executes mutable network-delivered code without verifying its contents or authenticity beyond HTTPS. Although the domain is consistent with the documented CLI provider and execution is conditional on a missing dependency, a compromised distribution endpoint could run arbitrary commands with the invoking account's privileges.
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 instructs an agent to execute downloaded shell or PowerShell code without a separate approval step or integrity verification. A missing CLI can therefore turn an ordinary Metabase request into local code execution; compromise of the installer source could expose files and credentials accessible to the agent's OS account.
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