The package's core API use is consistent with its stated memory service, and the Ellipsis token flow is conditional and directed to the configured Ellipsis API. However, a default MCP initialize silently registers the package's own lifecycle hooks, which is an agent extension lifecycle risk even though the README describes a separate explicit hook-install command.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The MCP client sends initialize; automatic hook setup is enabled unless SLASHML_DISABLE_AUTO_HOOKS=1.
Impact
Future agent events can invoke the package's hooks and send relevant prompt or tool context to SlashML's API; users may not expect this configuration change from starting the MCP server.
Mechanism
The server adds commands that run its own hook binary for prompt and tool lifecycle events and writes agent configuration files.
Evidence
bin/slashml-mcp.js~/.claude/settings.json~/.claude/CLAUDE.md~/.cursor/hooks.json~/.cursor/rules/slashml-memory.mdc~/.slashml/bin/slashml-hook.js