Skip to content

feat(mcp): strict MCP config mode (launcher allowlist) - #301

Open
raymondginger2018-sudo wants to merge 1 commit into
lessweb:mainfrom
raymondginger2018-sudo:feat/mcp-strict-config
Open

feat(mcp): strict MCP config mode (launcher allowlist)#301
raymondginger2018-sudo wants to merge 1 commit into
lessweb:mainfrom
raymondginger2018-sudo:feat/mcp-strict-config

Conversation

@raymondginger2018-sudo

Copy link
Copy Markdown

??

?? strict MCP config ??:??? MCP ????????????????(npx/node/python3/python/uvx/uv/bun/deno/go/java),??????? spawn ????????????,???????????????????

??

  • McpManager.setStrictMode() + connectServer ????????
  • settings.strictMcpConfig(????? STRICT_MCP_CONFIG)??
  • SessionManager.initMcpServers ??

??

  • ??????
  • ????:????????(Strict ??)?????????? spawn??????????

??

?????? PR #263 ???????(? PR ????)?

When settings.strictMcpConfig (or STRICT_MCP_CONFIG env) is enabled, MCP
servers may only be started by allowlisted launcher commands (npx/node/
python/uvx/bun/deno/go/java/...). A disallowed command fails fast with a
clear status before anything is spawned, so an untrusted config cannot run
arbitrary executables. Wired through SessionManager.initMcpServers.

Extracted from the earlier closed PR lessweb#263 (kept as a focused change).
@raymondginger2018-sudo

Copy link
Copy Markdown
Author

Hi maintainers. This PR comes from a fork, so its GitHub Actions workflow runs are currently in action_required state, waiting for a maintainer to approve. Could you approve the runs when you get a chance so CI can verify the change? Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant