DOCS-1739 - Required OAuth scopes for MCP Server tools#6878
Merged
Conversation
Add a Required scope column to the MCP tool tables, filled in where scope data is confirmed and marked TBD where it's still pending from engineering.
4 tasks
kimsauce
marked this pull request as draft
July 9, 2026 02:55
kimsauce
changed the title
Update the Available MCP Tools tables to match the tool set now live across production deployments: drop tools that were cut before GA (alert history/related alerts/resolve, delete dashboard, insight comments/history/related-entities/triage, enable rule, list users), replace the search-job tool set with the new runLogSearch tool, and add the new Discovery category. Fill in required OAuth scopes confirmed by engineering, replacing TBD placeholders. Prune example workflow prompts that depended on removed capabilities, and clean up the Prerequisites/Setup sections for accuracy and clarity. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
marked this pull request as ready for review
July 13, 2026 06:56
…p-tool-scopes # Conflicts: # docs/api/mcp-server.md
ganano
reviewed
Jul 13, 2026
…p-tool-scopes # Conflicts: # blog-cse/2026-07-09-application.md # cid-redirects.json # docs/api/mcp-server.md # docs/cse/get-started-with-cloud-siem/about-cse-insight-ui.md
Per ganano's PR review comment: x_amz_bedrock_agentcore_search has no required scope since it's built into the AWS AgentCore gateway rather than gated by a Sumo Logic permission. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
commented
Jul 13, 2026
amee-sumo
approved these changes
Jul 13, 2026
amee-sumo
left a comment
amee-sumo
left a comment
Collaborator
There was a problem hiding this comment.
Approving — this is a high-quality update. The scope column, GA tool-set reconciliation, expanded manual OAuth setup, and (notably thorough) pruning of example prompts that depended on removed tools all look correct. All internal anchors resolve and the category descriptions match their tables.
One requested change before merge (non-blocking for approval): the Log search :::note describes the Discovery tools as resolving _sourceCategory/_collector, but none of the three listed Discovery tools actually returns those. See the inline comment. Worth a quick reword or confirmation with engineering.
— via Claude Code
Per review comment: the Discovery tools (listCustomFields, listExtractionRules, listPartitions) identify a relevant _sourceCategory, but _collector values come from a separate scoped sample query, not the Discovery tools themselves. Also reworded the Discovery sample prompt to match what these tools actually return (partitions, extraction rules) instead of "source categories," which none of them list directly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kimsauce
enabled auto-merge
July 13, 2026 19:09
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
3 participants
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.
Purpose of this pull request
This pull request adds a "Required scope" column to the MCP Server tool tables, and updates the tool tables to match the tool set now live across all production deployments — confirmed by GN as the tool set going GA.
Changes:
runLogSearchtool, and added the new Discovery category (listCustomFields,listExtractionRules,listPartitions)x_amz_bedrock_agentcore_search) is marked N/A, since it's built into the AWS AgentCore gateway rather than gated by a Sumo Logic permissionmainfrom a separate PR while this one was open, and pruned example workflow prompts that depended on removed capabilitiesPreviously blocked pending the GA tool set shipping — that's now resolved, so this PR is unblocked and reflects the final GA tool set.
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1739