Skip to content

[mcp-tools] Update GitHub MCP toolsets mapping with Automation group and session/task tools #71906

Closed as not planned

Description

@github-actions

Tip

Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.


Summary

During this run's systematic self-inspection of the GitHub MCP remote server's read-accessible tools, I found discrepancies versus pkg/workflow/data/github_toolsets_permissions.json (v2.6) and fixed them:

  • Added to copilot toolset (confirmed present via self-inspection, missing from the mapping): get_automation_group, list_automation_groups, get_automations_configuration_for_repository, get_copilot_session_events, get_copilot_task_status.
  • Removed from issues toolset: semantic_issues_search — a stale duplicate entry whose documented description ("Search issues using natural language queries") matches the confirmed tool search_issues exactly, and which did not appear as a distinct tool during self-inspection.
  • Bumped mapping version to 2.7 and updated its description.
  • Updated (per-tool reference table for copilot and issues) and refreshed the "Last Updated" date in .

Methodology and important caveat

This agent runs with a read-only, restricted-toolset view of the GitHub MCP server (write operations and the context toolset are not exposed to this session's identity/guard-policy). So absence of a tool from self-inspection is only a meaningful signal for tools that are themselves read-only (no write side effects) — write tools and context-toolset tools were expected to be invisible this run and were not treated as removed.

Two other read-only tools already listed in the mapping (find_duplicate, issue_dependency_read in issues) were also not observed this run, but the existing docs already note these require upstream feature flags independent of toolset selection, so no change was made for those. get_file_blame (in repos) was likewise not observed; it may be similarly feature-flagged or consolidated elsewhere, but I did not have enough confidence to change the mapping, so I left it as-is — flagged for manual follow-up in the full tools report (published as a discussion).

No Go code was touched (JSON/Markdown only); JSON syntax was validated directly. The sandbox's Go toolchain could not be upgraded to the repo's required 1.27.3 without network access, so go build/tests could not be run locally for this change — the change is data/doc-only and low risk.

Test plan

  • Validated updated JSON parses correctly
  • Verified only the three intended files changed (github_toolsets_permissions.json, github-mcp-server-tools.md, github-mcp-server.md)
  • CI build/tests (could not run locally due to sandbox network/toolchain restrictions)

🤖 Generated with [Claude Code]((claude.com/redacted)


Note

Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by 📊 GitHub MCP Remote Server Tools Report Generator · claude · agent · ~136 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷

  • expires on Oct 27, 2026, 4:50 AM UTC-08:00

Activity

  1. github-actions commented on Oct 27, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-27T12:50:56.774Z.

    Closed by Workflow

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions