Security audit
Security checks for vulnerabilities and agentic risk
The Meta-reading workflow fits its purpose, but its setup can execute unverified remote installers without a clear approval step.
Review and install a verified CLI separately before enabling the skill, including its automatic skill-installation behavior. Connect only the Meta permissions you need and understand that OOMOL mediates account access. The concrete concern is uncontrolled setup behavior; credential theft and destructive Meta actions are not supported by the inspected artifact. External installers and backend behavior remain unverified.
The supplied command performs remote installation rather than searching or reading Meta data. No Meta access or dependency relationship is shown that would establish this as a supporting implementation detail. The downloaded script's contents are unavailable, so its additional behavior cannot be determined.
Authentication can support data access, but it is the entire behavior of the supplied chunk, with no demonstrated connection to Meta or implementation of searching and reading data. The supplied code therefore has a materially different primary purpose from the description.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_current_user` — Retrieve the current Meta Graph API user for the connected access token.
- `get_insights` — Retrieve Meta Ads insights for an ad account, campaign, ad set, or ad object.
- `list_ad_accounts` — List Meta ad accounts available to the connected access token.
- `list_campaigns` — List campaigns under one Meta ad account with optional delivery status filters.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_current_user` — Retrieve the current Meta Graph API user for the connected access token.
- `get_insights` — Retrieve Meta Ads insights for an ad account, campaign, ad set, or ad object.
- `list_ad_accounts` — List Meta ad accounts available to the connected access token.
- `list_campaigns` — List campaigns under one Meta ad account with optional delivery status filters.
## Safety
Piping an unpinned HTTPS download directly into bash executes whatever the installer endpoint returns with the agent process's local privileges. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from delivering code that steals accessible data or alters the system; this overlaps with SQP-2.
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 an agent to execute remotely fetched shell or PowerShell code without first obtaining approval for installation and local system changes. Although conditional on a missing CLI, it turns a read-oriented Meta request into local code execution whose behavior is not constrained by the skill.
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