Security audit
Security checks for vulnerabilities and agentic risk
Teable data changes require approval, but first-time setup directs the agent to execute unverified remote software without a separate approval step.
Review the setup before installing. Approve and verify the CLI separately, including any additional agent skills it installs; the remote installers could not be inspected. OOMOL mediates access to your connected Teable account, so limit that connection to the permissions needed. Keep the documented approval steps for edits and deletions.
The supplied chunk performs remote installer execution, not Teable data operations. Although dependency installation can be a supporting implementation detail, nothing supplied establishes this installer's role in accessing Teable. The downloaded script is not included, so its additional behavior cannot be assessed.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_records` — Create one or more records in a Teable table using provider-defined field values. [write]
- `delete_record` — Permanently delete one Teable record by table ID and record ID. [destructive]
- `get_current_user` — Get the Teable user associated with the connected personal access token.
- `get_record` — Get one Teable record by table ID and record ID.
- `list_bases` — List the Teable bases in a space accessible to the connected token.
- `list_records` — List records in a Teable table with optional projection, view, filtering, sorting, and offset pagination.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_record` — Get one Teable record by table ID and record ID.
- `list_bases` — List the Teable bases in a space accessible to the connected token.
- `list_records` — List records in a Teable table with optional projection, view, filtering, sorting, and offset pagination.
- `list_spaces` — List the Teable spaces accessible to the connected personal access token.
- `list_tables` — List the Teable tables in a base accessible to the connected token.
- `update_record` — Update the fields of one Teable record by table ID and record ID. [write]
Piping an HTTPS response directly into bash executes mutable remote code with the invoking user's privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint or malicious installer update could access local data or modify the system; the missing-CLI condition reduces exposure frequency but does not remove this 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 fallback directs the agent to execute a remote installer without explaining its local execution privileges or requiring approval for software installation. Although conditional on a missing dependency, this expands a Teable data request into local system changes that the user may not have authorized; the declared oo-only tool restriction may constrain execution but is not an installation-consent safeguard.
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