fix(slack): avoid per-channel metadata lookups - #1348
Draft
akshaan wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
The Slack channels endpoint fetched metadata sequentially for every permitted channel. A User MCP role with 909 public channels could not finish within the Slack client timeout, so fallback search timed out before it could scan channel history.
Permission behavior
This does not broaden channel access. The endpoint still returns only channel IDs present in the caller JWT claims; the workspace-wide public catalog is used only to enrich those already-authorized IDs with metadata. Missing IDs retain the existing conversations.info path.
Validation