kerneldev-mcp

The server heavily relies on `subprocess.run` and `subprocess.Popen` to execute system commands (`make`, `git`, `lvm` tools, `virtme-ng`, `qemu`, `sudo`). It is designed for kernel developers with appropriate system privileges. The documentation explicitly states that it requires `sudo` access for many operations (e.g., LVM device management, `modprobe`, `chown`) without password prompts, implying a trust relationship with the user running the MCP server. Arbitrary shell commands/scripts can be executed inside isolated VMs via `boot_test` and `boot_with_custom_command` tools, which is documented as intentional for flexibility and requires trusted input. There is no direct `eval` from user input in the core server logic. Remote code execution would be possible if the server is run by an untrusted user with configured passwordless sudo access.