Skip to content

[mcp-tools] Update GitHub MCP toolsets mapping: add issue dependency tools#45082

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
update-github-mcp-tools-mapping-ff3696aee8d4b647
Open

[mcp-tools] Update GitHub MCP toolsets mapping: add issue dependency tools#45082
github-actions[bot] wants to merge 2 commits into
mainfrom
update-github-mcp-tools-mapping-ff3696aee8d4b647

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

Adds two newly-available tools to the issues toolset in pkg/workflow/data/github_toolsets_permissions.json to match the current github/github-mcp-server source.

Added tools (issues toolset)

Tool Type Toolset Source
issue_dependency_read read issues issue_dependencies.go
issue_dependency_write write issues issue_dependencies.go

Both are registered in the AllTools inventory under ToolsetMetadataIssues. The existing read_permissions/write_permissions for the issues toolset (issues) already cover them, so no permission changes were needed. Tools remain in alphabetical order.

Not added (intentionally)

  • Granular issue/PR tool variants (issues_granular / pull_requests_granular feature flags) — feature-flagged OFF by default; they replace the consolidated issue_write/update_pull_request tools only when opted in via the X-MCP-Features header.
  • ui_get — insiders-only, not part of the standard remote toolset.

Flagged for follow-up (no change in this PR)

check_dependency_vulnerabilities (currently listed under security_advisories) no longer appears in the github-mcp-server source registration and may have been removed upstream. It was left in place pending verification against the live remote MCP server, since the gateway was not directly reachable from this run.

Discovery method

Toolset membership was cross-referenced against the github-mcp-server main source (pkg/github/tools.go AllTools, issue_dependencies.go) because the MCP gateway was network-isolated from the agent sandbox this run.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 📊 GitHub MCP Remote Server Tools Report Generator · 264.7 AIC · ⌖ 13.6 AIC · ⊞ 10.5K ·

  • expires on Jul 14, 2026, 4:49 AM UTC-08:00

Add issue_dependency_read and issue_dependency_write to the issues
toolset to match the current github/github-mcp-server source.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added automation documentation Improvements or additions to documentation labels Jul 12, 2026
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor Author

Hey @github-actions 👋 — thanks for this automated update to the MCP toolsets mapping, adding issue_dependency_read and issue_dependency_write to the issues toolset! The change is well-scoped and the PR description is thorough, including a clear rationale for what was intentionally omitted.

One small thing that would strengthen this:

  • Add or update a testpkg/workflow/data/github_toolsets_permissions.json is a data file but if there are snapshot or validation tests covering the toolset inventory, they should be updated to include the two new tool entries.

If you'd like a hand, you can assign this prompt to your coding agent:

Check whether there are any tests or validation fixtures that cover pkg/workflow/data/github_toolsets_permissions.json.
If so, update them to include the two new entries added in this PR:
- issue_dependency_read (read, issues toolset)
- issue_dependency_write (write, issues toolset)
Ensure all existing tests still pass after the update.

Generated by ✅ Contribution Check · 128.4 AIC · ⌖ 10.6 AIC · ⊞ 6.2K ·

@gh-aw-bot

Copy link
Copy Markdown
Collaborator

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29196572530

Generated by 👨‍🍳 PR Sous Chef · 8.11 AIC · ⌖ 5.41 AIC · ⊞ 4.2K ·
Comment /souschef to run again

…st coverage

Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>

Copilot AI commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29196572530...

Done. The contribution-check feedback pointed to missing test coverage and a missing entry in github_tool_to_toolset.json (the file used for runtime tool validation).

Changes in commit fix: add issue_dependency tools to github_tool_to_toolset.json and test coverage:

  • Added issue_dependency_read and issue_dependency_write to pkg/workflow/data/github_tool_to_toolset.json (the original PR only updated github_toolsets_permissions.json)
  • Added 4 new test cases to TestValidateGitHubToolsAgainstToolsets covering both tools
  • Added both tools to TestGitHubToolToToolsetMap_ConsistencyWithDocumentation

Local validation passes: make fmt, make lint, make test-unit, make agent-report-progress all green.

Copilot AI requested a review from gh-aw-bot July 12, 2026 14:58
@gh-aw-bot

Copy link
Copy Markdown
Collaborator

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29200137487

Generated by 👨‍🍳 PR Sous Chef · 8.57 AIC · ⌖ 7.74 AIC · ⊞ 7.5K ·
Comment /souschef to run again

Copilot AI commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29200137487...

No new issues found. The PR is already in merge-ready state from the previous pass (commits 2c888d1 and f0ab87d). The Sous Chef run that triggered this had no new findings. Local tests still green.

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

Labels

automation documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants