Security audit
Security checks for vulnerabilities and agentic risk
The cloud-reading workflow fits its purpose, but setup tells the agent to execute downloaded installers without verification or a separate approval step.
Review and approve the CLI installation separately, preferably using a verified, pinned release, and use read-only CrateDB credentials. Consider OOMOL's access to your connection and results, plus the CLI's additional agent-skill installation behavior. The bundled instructions were fully inspected; downloaded software and live connector behavior remain unverified.
The supplied command executes an Oomol-hosted installer, with no visible CrateDB Cloud interaction. This is a materially different capability from the declared data-access purpose, and the supplied content establishes no connection that would justify it as a supporting implementation detail. The downloaded script's contents and further effects are not shown.
The command pipes a mutable remote script directly into bash without pinning or independently verifying its contents. Compromise of the distribution endpoint or release process could execute arbitrary code with the agent's local permissions; HTTPS protects transport but does not establish that the script itself is safe.
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 the agent to execute downloaded shell or PowerShell code without first explaining the system changes or obtaining approval. A missing CLI can therefore turn a read-only cloud request into local software installation with the agent's operating-system permissions, exceeding the apparent scope of the user's request.
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