muav_gui_mcp

The server uses Zod for input validation, which is generally good for defined schemas. However, critical tools like 'send_command', 'ros_service_call', and 'pub_ros_topic' accept 'z.any()' or 'z.object({}).passthrough()' for command attributes and ROS message payloads. This design delegates all validation of these potentially dangerous, robot-controlling inputs to the backend API (specified by MUAV_API_URL). If the backend API is not sufficiently robust in sanitizing or validating these arbitrary inputs, it could lead to command injection, unexpected robot behavior, or system compromise through malformed requests. Environment variables for API URL and token prevent hardcoded secrets but rely on secure environment management. Error messages from API calls are stringified and returned, which could expose internal server details. CORS is commented out in 'httpStreamableSever', but if enabled with permissive origins, it could introduce a web security risk.