The bundled MCP tool forwards OPENAI_API_KEY or a generic API_KEY to api.hanzo.ai when HANZO_API_KEY is absent. Because the code does not verify that the fallback credential belongs to Hanzo, this is a real credential-handling risk, though the path is triggered by tool use rather than installation.
Static reason
One or more suspicious static signals were detected.
Trigger
The MCP tool is invoked with an API key available in the environment; absent HANZO_API_KEY, it falls back to API_KEY or OPENAI_API_KEY.
Impact
A credential intended for another AI service may be disclosed to Hanzo when the tool is used.
Mechanism
The tool uses the selected key as a Bearer token for a POST to the configured API URL, which defaults to https://api.hanzo.ai/v1.
Evidence
.lpm-dependency-evidence-e8b4b303-b0a7-4581-ace9-5a6e8ad37be9/0/npm-linux/dist/cli.js
Network endpoints2
api.hanzo.ai/v1/chat/completionsgithub.com/hanzoai/dev/releases/download/v${version}/${archiveName}