Security audit
Security checks for vulnerabilities and agentic risk
The Namely integration fits its stated purpose, but missing-CLI setup directs the agent to execute unverified downloaded code without a clear approval step.
Review and approve CLI installation separately before allowing automatic setup, including its bundled-skill installation behavior. Connect only an authorized Namely account with the minimum employee-data access needed, and consider OOMOL's role in handling authentication and requests. The downloaded installer and hosted connector implementation were not verified.
The supplied command performs remote code execution from an Oomol installation endpoint rather than searching or reading Namely data. Nothing in the supplied chunk establishes that this installation is a supporting dependency for Namely access. The downloaded script's contents and further effects are not available for assessment.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_current_profile` — Get the Namely profile associated with the personal access token.
- `get_profile` — Get one Namely employee profile by profile ID.
- `list_profile_fields` — List Namely profile fields configured for the company.
- `list_profiles` — List Namely employee profiles visible to the personal access token.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_current_profile` — Get the Namely profile associated with the personal access token.
- `get_profile` — Get one Namely employee profile by profile ID.
- `list_profile_fields` — List Namely profile fields configured for the company.
- `list_profiles` — List Namely employee profiles visible to the personal access token.
## Safety
Piping a mutable HTTPS response directly into bash executes remote code without a pinned version or independent integrity verification. Compromise of the installer distribution path could execute attacker-controlled code with the user's privileges; the conditional setup trigger reduces exposure but does not remove this supply-chain risk, and the PowerShell alternative has the same weakness.
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 execute downloaded shell or PowerShell installation code without requiring informed approval for local system changes. Although conditional and relevant to setup, this expands a read-oriented Namely task into arbitrary code execution with the invoking user's privileges; actual execution also depends on the agent's tool permissions.
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