Security audit
Security checks for vulnerabilities and agentic risk
The MotherDuck workflow includes clear approval controls, but setup can execute unverified remote software without separate user approval.
Review and approve CLI installation separately, preferably using a pinned, verified release. Check its bundled-skill installation behavior and connect only the MotherDuck permissions you need. Preserve the skill's explicit confirmations for account changes and deletions. The remote installer and connector implementations were not verified; the artifact does not establish credential theft or malicious intent.
The supplied command executes an Oomol-hosted installer, with no visible MotherDuck interaction or established connection to the declared functionality. This is a materially different operation, not a demonstrated supporting implementation detail. 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
- `create_token` — Create a MotherDuck access token for a user. [write]
- `create_user` — Create a MotherDuck member user in the organization. [write]
- `delete_token` — Invalidate a MotherDuck access token for a user. [destructive]
- `delete_user` — Permanently delete a MotherDuck user and all of their data. [destructive]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_token` — Create a MotherDuck access token for a user. [write]
- `create_user` — Create a MotherDuck member user in the organization. [write]
- `delete_token` — Invalidate a MotherDuck access token for a user. [destructive]
- `delete_user` — Permanently delete a MotherDuck user and all of their data. [destructive]
- `get_user_duckling_config` — Retrieve MotherDuck Duckling configuration for a user.
- `list_active_accounts` — List active MotherDuck accounts and their active Ducklings in the organization.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `delete_user` — Permanently delete a MotherDuck user and all of their data. [destructive]
- `get_user_duckling_config` — Retrieve MotherDuck Duckling configuration for a user.
- `list_active_accounts` — List active MotherDuck accounts and their active Ducklings in the organization.
- `list_tokens` — List MotherDuck access tokens for a user.
- `set_user_duckling_config` — Set MotherDuck Duckling configuration for a user. [write]
## Safety
Piping an HTTPS response directly into bash executes mutable remote code without pinning a version or independently verifying its integrity. Compromise of the installer endpoint or distribution infrastructure could execute attacker-controlled code with the agent process's permissions; the setup-only condition reduces exposure 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 missing-CLI fallback directs the agent to execute remotely downloaded shell or PowerShell code without requiring installation-specific approval or explaining the system changes. Although conditional and relevant to setup, this can turn an ordinary MotherDuck request into arbitrary code execution with the agent process's 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