Security audit
Security checks for vulnerabilities and agentic risk
Postman changes require user approval, but setup directs the agent to execute an unverified remote installer without a separate approval step.
Review setup before installing. Prefer a separately approved CLI release with verified integrity, and inspect or disable its automatic skill synchronization. Connect only the Postman account and permissions needed, and retain the explicit approval requirements for writes and deletions. The submitted skill was fully inspected, but the remote installer and hosted connector implementation were not verified. No artifact-backed malicious intent was found.
The supplied command contains no Postman operations and instead executes an installer from an unrelated service. Nothing in the supplied content establishes that this installation supports the declared Postman functionality. The remote script's contents are not supplied, so its specific effects cannot be determined.
The command downloads a mutable remote script and immediately executes it without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the installer distribution path could execute attacker-controlled code with the agent process's local privileges, exposing accessible files and credentials. The legitimate dependency and missing-CLI condition reduce exposure but do 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 install software after a missing-command error without explicitly obtaining approval for local system changes. A user authorizing a Postman operation has not necessarily authorized executing an installer on their machine; the conditional trigger limits exposure but does not establish consent.
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