bead-mcp-ts

The server relies heavily on executing the external 'bd' CLI via 'child_process.spawn'. While 'spawn' is generally safer than 'exec', user-provided strings (like titles, descriptions, assignee names, etc.) are passed directly as arguments. This introduces a risk if the 'bd' CLI itself has vulnerabilities that allow command injection or improper handling of malicious input in its arguments. Path resolution for 'workspace_root' also involves `git rev-parse` and file system checks, which, if not properly sanitized or if user input is fully untrusted, could lead to unexpected behavior or information disclosure, although no direct write vulnerabilities are apparent. No 'eval' or hardcoded secrets found.