Security audit
Security checks for vulnerabilities and agentic risk
The LaunchDarkly workflow has clear approval safeguards, but its setup instructions run downloaded software without a separate approval or verification step.
Review and approve CLI installation separately, including its bundled-skill changes, rather than letting a LaunchDarkly request trigger the download-and-run fallback. Use a verified installation and narrowly scoped LaunchDarkly credentials, and retain the required write and deletion approvals. OOMOL mediates account access; its hosted connector and remote installer implementations were not verified in this review.
The supplied command installs software from Oomol rather than performing LaunchDarkly operations. Nothing in the code establishes this installation as a supporting dependency for the declared purpose. The downloaded script's contents and further effects are not available in the supplied chunk.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_project` — Create a LaunchDarkly project using either common fields or a full official request body. [write]
- `create_segment` — Create a LaunchDarkly segment using either common fields or a full official request body. [write]
- `create_team` — Create a LaunchDarkly team using either common fields or a full official request body. [write]
- `create_token` — Create a LaunchDarkly access token using either common fields or a full official request body. [write]
- `delete_environment` — Delete a LaunchDarkly environment by project key and environment key. [destructive]
- `delete_feature_flag` — Delete a LaunchDarkly feature flag by project key and feature flag key. [destructive]
- `delete_project` — Delete a LaunchDarkly project by project key. [destructive]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `patch_project` — Patch a LaunchDarkly project with standard JSON Patch operations. [write]
- `patch_segment` — Patch a LaunchDarkly segment with JSON Patch, JSON Merge Patch, or semantic patch instructions. [write]
- `patch_team` — Patch a LaunchDarkly team with semantic patch instructions. [write]
- `patch_token` — Patch a LaunchDarkly access token with standard JSON Patch operations. [write]
- `reset_token` — Reset a LaunchDarkly access token value and optionally control when the old value expires. [destructive]
- `search_context_instances` — Search LaunchDarkly context instances in a project environment with filtering, sorting, and pagination.
- `search_contexts` — Search LaunchDarkly contexts in a project environment with filtering, sorting, and pagination.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `patch_segment` — Patch a LaunchDarkly segment with JSON Patch, JSON Merge Patch, or semantic patch instructions. [write]
- `patch_team` — Patch a LaunchDarkly team with semantic patch instructions. [write]
- `patch_token` — Patch a LaunchDarkly access token with standard JSON Patch operations. [write]
- `reset_token` — Reset a LaunchDarkly access token value and optionally control when the old value expires. [destructive]
- `search_context_instances` — Search LaunchDarkly context instances in a project environment with filtering, sorting, and pagination.
- `search_contexts` — Search LaunchDarkly contexts in a project environment with filtering, sorting, and pagination.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `delete_project` — Delete a LaunchDarkly project by project key. [destructive]
- `delete_segment` — Delete a LaunchDarkly segment by project key, environment key, and segment key. [destructive]
- `delete_team` — Delete a LaunchDarkly team by team key. [destructive]
- `delete_token` — Delete a LaunchDarkly access token by token identifier. [destructive]
- `get_caller_identity` — Get the LaunchDarkly caller identity for the current access token.
- `get_context_instances` — Get a LaunchDarkly context instance by project key, environment key, and context instance identifier.
- `get_contexts` — Get a LaunchDarkly context by context kind and key, with optional paging over related results.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `delete_segment` — Delete a LaunchDarkly segment by project key, environment key, and segment key. [destructive]
- `delete_team` — Delete a LaunchDarkly team by team key. [destructive]
- `delete_token` — Delete a LaunchDarkly access token by token identifier. [destructive]
- `get_caller_identity` — Get the LaunchDarkly caller identity for the current access token.
- `get_context_instances` — Get a LaunchDarkly context instance by project key, environment key, and context instance identifier.
- `get_contexts` — Get a LaunchDarkly context by context kind and key, with optional paging over related results.
- `get_environment` — Get a LaunchDarkly environment by project key and environment key.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_segments` — List LaunchDarkly segments in a project environment with optional filtering and pagination.
- `get_tags` — List LaunchDarkly tags with optional prefix and resource-kind filters.
- `get_team` — Get a LaunchDarkly team by team key.
- `get_token` — Get a LaunchDarkly access token by token identifier.
- `get_tokens` — List LaunchDarkly access tokens with optional pagination and visibility scope.
- `list_projects` — List LaunchDarkly projects with optional filtering, sorting, pagination, and expansion.
- `list_teams` — List LaunchDarkly teams with optional filtering, pagination, and expansion controls.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_tags` — List LaunchDarkly tags with optional prefix and resource-kind filters.
- `get_team` — Get a LaunchDarkly team by team key.
- `get_token` — Get a LaunchDarkly access token by token identifier.
- `get_tokens` — List LaunchDarkly access tokens with optional pagination and visibility scope.
- `list_projects` — List LaunchDarkly projects with optional filtering, sorting, pagination, and expansion.
- `list_teams` — List LaunchDarkly teams with optional filtering, pagination, and expansion controls.
- `patch_environment` — Patch a LaunchDarkly environment with standard JSON Patch operations. [write]
The command pipes a mutable remote response directly into Bash without version pinning, independent integrity verification, or review. Compromise of the installer distribution path could execute attacker-controlled code with the agent's local privileges; HTTPS and the legitimate setup purpose do not eliminate that supply-chain risk.
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 missing-CLI fallback directs execution of downloaded shell or PowerShell code without a separate approval step or explanation of potential system changes. Although conditional and relevant to setup, it can turn an ordinary LaunchDarkly request into local code execution with the agent'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