liara-mcp

The core server primarily acts as a proxy to the Liara API over stdio, limiting direct external network attack surface from tool calls. API tokens are expected to be provided via environment variables, which is good practice. The `bin/setup.js` script uses `execSync` for initial setup commands (e.g., `npm install -g`) which carries inherent risks, but this is for setup, not runtime execution. The `unwrapApiResponse` function uses broad `any` types for parsing, which could be less robust to unexpected API response formats but doesn't present an immediate execution vulnerability. There are no obvious hardcoded secrets in the runtime code. The `execCommand` service function, designed for running commands in app containers, explicitly delegates to external tools (like `liara app shell`) rather than executing arbitrary commands on the MCP server itself.