Security audit
Security checks for vulnerabilities and agentic risk
This Oracle Cloud management skill needs review because it misclassifies a potentially disruptive action and executes an unverified installer during setup.
Before installing, require explicit approval for instance_action and verify the target and effect. Review a fixed CLI release and its installation behavior, including automatic changes to agent skills. Use narrowly scoped Oracle credentials and understand that OOMOL mediates account operations. The external installer and hosted connector implementation were not audited.
The supplied command performs remote installer execution, not an OCI operation. Although installing dependencies can be a supporting implementation detail, this chunk provides no evidence connecting the Oomol installer to the declared OCI purpose. The downloaded script's contents and any further effects are not available for assessment.
The fallback installation command immediately executes remotely downloaded shell code without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or release pipeline is compromised, an installation attempt could execute arbitrary code with the local user's privileges and expose local credentials, although the missing-CLI condition limits when this path is reached.
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 skill leaves instance_action untagged while explicitly instructing the agent to treat all untagged actions as reads that are safe to run directly. Instance lifecycle actions can change operational state, so this classification can bypass user confirmation and cause outages; fetching the input schema does not correct the missing approval requirement.
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