Security audit
Security checks for vulnerabilities and agentic risk
The JumpServer reads fit the stated purpose, but setup can execute a remote installer without separate approval or integrity verification.
Review and explicitly approve CLI setup before allowing the agent to install it. Check the CLI's documented skill synchronization and disable unwanted changes to other agent hosts. Use narrowly scoped, read-only JumpServer credentials and consider OOMOL's handling of requested records. The remote installer and connector implementation were not inspected.
The supplied command performs remote script execution rather than searching or reading JumpServer data. Nothing in the provided code establishes that this installer is a supporting dependency for JumpServer access. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
Piping a remotely fetched script directly into Bash executes its contents without version pinning or independent integrity verification; the PowerShell alternative has the same issue. A compromised distribution endpoint or malicious installer update could execute arbitrary code with the agent process's privileges, potentially exposing local files and credentials. HTTPS and the missing-CLI prerequisite reduce some exposure but do not establish the installer's integrity.
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 when a read-oriented request encounters a missing CLI, without first obtaining approval for local system changes. Although conditional and operationally relevant, this expands the user's requested data access into execution of an installer with the current user's privileges.
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