fwerkor/local-shell-mcp
C3Enables LLM to use a cli environment.
★ 10+ · fwerkor/local-shell-mcp source on GitHub · this plugin in the registry
fwerkor/local-shell-mcp is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes system commands, decodes base64 payloads.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer |
| executes system commands | exec | ×7 src, e.g. npm/bin/local-shell-mcp.js:4, npm/bin/local-shell-mcp.js:107 |
| decodes base64 payloads | base64_decode | ×8 src, e.g. ui/src/live-workspace.ts:1115, src/local_shell_mcp/ui_static/web.js:9 |
| reads credential-class env vars | token_env | LOCAL_SHELL_MCP_UI_LOCAL_TOKEN |
Services it injects
agents conversation sessions slots systemPrompt tools webServer
Hooks it attaches
session/disposed
Environment variables it reads
LSM_UI_BINARY_OUTDIR LOCAL_SHELL_MCP_NPM_CACHE LOCALAPPDATA LOCAL_SHELL_MCP_BINARY LOCAL_SHELL_MCP_UI_CELL_ASPECT LOCAL_SHELL_MCP_UI_MODE XDG_CACHE_HOME OPENTUI_LIBC LOCAL_SHELL_MCP_UI_API_BASE LOCAL_SHELL_MCP_UI_LOCAL_TOKEN
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.