nix-mcp

The server wraps Nix CLI commands using `subprocess.run` with a list of arguments, which generally mitigates common shell injection risks. There are no explicit uses of Python's `eval()` or obfuscation. The primary security consideration is that the server directly exposes powerful Nix functionalities (like building, evaluating, and searching) to an LLM. While `extra_args` allows for flexible command line additions, it is appended as separate arguments to the Nix command, making direct shell injection difficult. However, a malicious or poorly instructed LLM could potentially pass Nix-specific arguments or expressions that lead to resource exhaustion, information leakage, or unwanted system modifications through Nix itself, rather than a flaw in the server's code. Logs are written to `/tmp` which can aid auditing.