Skip to content

fix(everything): limit get-env to one key#4164

Open
Lubrsy706 wants to merge 1 commit into
modelcontextprotocol:mainfrom
Lubrsy706:fix/everything-get-env-key
Open

fix(everything): limit get-env to one key#4164
Lubrsy706 wants to merge 1 commit into
modelcontextprotocol:mainfrom
Lubrsy706:fix/everything-get-env-key

Conversation

@Lubrsy706
Copy link
Copy Markdown

Summary

  • require a key argument for the get-env demo tool
  • return only that environment variable plus a found flag instead of dumping process.env
  • add tests and update docs to reflect the narrower contract

Fixes #3986.

Tests

  • npm test -- __tests__/tools.test.ts
  • npm run build

@Lubrsy706 Lubrsy706 force-pushed the fix/everything-get-env-key branch from cee615d to 2f9cc00 Compare May 18, 2026 02:36
@Lubrsy706
Copy link
Copy Markdown
Author

Rebased this branch onto the latest main and resolved the get-env conflict by keeping the new single-key input schema together with the current tool annotations. Local checks passed: npm run build --workspace @modelcontextprotocol/server-everything and npm test --workspace @modelcontextprotocol/server-everything -- __tests__/tools.test.ts. The refreshed PR checks are green as well.

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.

server-everything: get-env tool returns full process.env without any filtering

1 participant