docx-mcp: why it is not safe to use

What we found

Our review did not identify a security or privacy issue that would block use of `docx-mcp`. In the inspected README, install script, and server entrypoints, we did not find hidden instructions, disguised behavior, or intentionally obscured payloads. The repository materials indicate local DOCX processing and local skill installation, and we did not find code that sends document contents to an undisclosed third party. We also did not find hardcoded credentials, API keys, or token material in the inspected files.

We noted that the skill can overwrite files and perform permanent redaction when explicitly invoked. Based on the inspected code, we did not find evidence of automatic irreversible actions without a user-directed tool call. We also did not find runtime remote code fetch and execution in the Python entrypoints, although the README does disclose an optional `curl`-to-shell installer alongside standard package-manager installation.

What to do instead

If you use this skill, prefer the standard package-manager install path over any `curl`-to-shell option, review file paths before running write or redaction actions, and test on copies of documents when possible.