Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.
Telemetry disclosureUndisclosed egress detected.Static checks found network calls the docs do not mention. Disclosed telemetry is common and fine, silent telemetry is the finding.
Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean Install-time hooks & dependenciesno flags
Code that runs when you install it, before you ever call a tool.
Runs code / shell commandsno flags
Whether the server can execute commands on your machine.
Secrets & credentialsno flags
How it reads, logs, or transmits keys and tokens. Scam/wallet-drainer patterns land here.
Network calls out2 findings
MEDIUMsrc/constants.ts:6 — Hardcoded external endpoint 'clarity.microsoft.com'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.
MEDIUMsrc/instructions.ts:63 — Hardcoded external endpoint 'www.example.com'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.
Prompt-injection passthrough1 finding
INFOsrc/utils.ts — HEURISTIC: this file both fetches external content and returns content as tool output, with no obvious sanitization. External text returned into tool output can carry instructions an agent obeys (prompt-injection passthrough). Confirm manually; this is a hint, not proof.
Permission scope breadthno flags
How much access it asks for versus what its job needs.
How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.
