Omniverse_USD_MCPServer_byJPH2

The server uses `json.loads` for response parsing and `subprocess.Popen` in its client/tester for starting the server itself, not arbitrary user input. There are no obvious signs of `eval` or direct code injection vulnerabilities. However, the server exposes file system operations (`create_new_stage`, `open_usd_stage`) that accept arbitrary `file_path` inputs, lacking explicit path validation to prevent directory traversal or writing to sensitive system locations. Network protocols (`http`, `websocket`, etc.) can be bound to `0.0.0.0`, requiring proper external firewalling and security measures for production deployments. Resource exhaustion is a potential risk if stages are continuously created/opened without external rate limiting. The README explicitly notes it is 'WIP' and requires significant hardening for enterprise use.