logseq-mcp@0.8.1
VERIFIEDPublisher claims: "Logseq Model Context Protocol Agent" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-29 and scored it 85/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
0.5sprocessdependency install exit 1
0.6sprocessexec /usr/bin/timeout
0.6sprocessexited 1: Node.js v22.23.4
0.6sclaimedno tools/list reply (exit 1)
0.6sprocessscript backend runs setup only
Static findings
MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.js:2 · MCP server using network transport (SSE/HTTP) — data sent over networkFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04CRITICAL
Prompt injectionREADME.md:45 · Prompt injection — known jailbreak technique referenceFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01MEDIUM
File permission modification commandpackage.json:37 · File permission modification command — agent changes file ownership/permissionsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05HIGH
Authorization escalation languageREADME.md:45 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01