Security audit
Security checks for vulnerabilities and agentic risk
The 7shifts features fit their stated purpose, but setup can run unverified remote installers and introduce undisclosed changes to agent skills.
Review the CLI installation separately before allowing the setup fallback. Use a reviewed release, check which agent skills it installs or updates, and disable automatic skill synchronization if unwanted using the [documented controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Connect only the necessary 7shifts permissions and account for OOMOL processing the requests. The remote installers and hosted connector were not audited; no malicious behavior was established in the supplied artifact.
The supplied command performs remote code execution for an apparent CLI installation, not searching or reading 7shifts data. No connection between this installer and the declared 7shifts functionality is established in the supplied chunk. The downloaded script's further behavior is unknown.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_company` — Retrieve one 7shifts company by ID.
- `list_companies` — List 7shifts companies available to the access token.
- `list_departments` — List 7shifts departments for a company.
- `list_locations` — List 7shifts locations for a company.
- `list_roles` — List 7shifts roles for a company.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `list_locations` — List 7shifts locations for a company.
- `list_roles` — List 7shifts roles for a company.
- `list_users` — List 7shifts users for a company.
- `retrieve_identity` — Retrieve the 7shifts identity associated with the access token.
## Safety
Piping a downloaded script directly into Bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell fallback has the same weakness. Compromise of the vendor's delivery infrastructure could execute attacker-controlled code with the agent process's local permissions, although HTTPS and the conditional setup path reduce some exposure.
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 tells the agent to install software when the CLI is missing without first explaining local changes or obtaining installation approval. This crosses from a read-only service request into local code execution; the missing-command prerequisite limits exposure but does not authorize that change.
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