mcp-framework

The `stdio` connector utilizes `std::process::Command` to spawn subprocesses. While the provided examples use trusted commands (e.g., `npx @playwright/mcp`), custom or untrusted command strings passed to `McpClient::new` or `MCPServerConfig::from_command` can lead to arbitrary command execution. Developers must ensure that inputs configuring `stdio` connections are validated and originate from trusted sources. The web-based Inspector (debug UI) binds to `127.0.0.1:8123` by default, limiting external network exposure. However, it exposes API endpoints (`/api/call-tool`) that allow interactive execution of registered tools, which could be abused by a local user or another process if tools have unintended side effects or vulnerabilities. Hardcoded API keys or sensitive credentials are not present; the framework correctly uses environment variables.