Repository navigation
Description
Thanks for the remote MCP server. We use it through Claude, where each tool's description is what the assistant, and the person approving a call, read before using it. Most descriptions do that well. These eleven leave something to guess:
actions_get: whether the artifact and log methods return the file or a link to it.actions_run_trigger: that deleting run logs is permanent, and what the call returns.add_comment_to_pending_review: how to start the pending review it needs. It says to ask the user, not thatpull_request_review_writecreates one; and what the call returns.issue_write: whether labels and assignees given on an update are added to the existing ones or replace them (the REST API replaces them), and whether it handles pull requests, as its title says, or only issues, as its description says.merge_pull_request: which merge method is used when none is given, whatexpectedHeadShaguards, and that a merge is undone only by a revert.push_files: whether files already at those paths are replaced, since it asks for none of the version checkcreate_or_update_filerequires, and whether the branch must already exist.request_copilot_review: whether it needs a Copilot plan or uses paid Copilot requests, and that the review arrives later on the pull request, not in the reply.run_secret_scanning(minor): why a repository must be named when the content is passed in.search_pull_requests: it says it takes GitHub's search syntax, but gives no example or qualifier, and nothing warns thatsearch_issuesbeside it matches natural language instead, so the same query behaves differently in the two.sub_issue_write: it says "add", but it also removes and reorders sub-issues; and where to find a sub-issue's ID, which is not its number.update_pull_request_branch(minor): whether the base branch's changes arrive by a merge or a rebase, and whatexpectedHeadShaguards.
Titles: the four Actions tools put "GitHub" in their titles, which a client already shows as the server's name; pull_request_review_write's title, "Write operations (create, submit, delete) on pull request reviews", is not a verb phrase; and "Run Secret Scanning" is in title case where the others use sentence case.
Hints: of the 19 tools that change things, only delete_file and actions_run_trigger set destructiveHint. On the other 17 it is unset, which the MCP specification reads as possibly destructive, so a client warns on every one. Setting it to false where a tool only adds or updates would let clients warn only where it matters.
Activity
rafe-walker commentedon Nov 9, 2026
On item 6 (
push_filesasks for no version check): a live repro showing it is not only a documentation gap. A push from a stale read silently overwrites another writer's change to that file (their commit stays in history; the file content reverts).Tested on v2.1.0 (image
sha256:f6056fc1…0f8a) and main nightly 99d6d65, same result on both:testhasp4/stale.txt=v0. Agent A reads it (get_file_contents).PUT /contentswith the current sha) tov1-by-agent-B→ commitC_B.{"name":"push_files","arguments":{"owner":"OWNER","repo":"REPO","branch":"test","message":"edit","files":[{"path":"p4/stale.txt","content":"v0 edited by agent A"}]}}C_B, and the file is nowv0 edited by agent A. B's change to the file is gone, with no error or warning to either agent.create_or_update_filerefuses the same write, because it checkssha.push_filesbuilds the tree on whatever head is current (pkg/github/repositories.go:1809-1841).UpdateRefwithForce: falseonly rejects a ref that moved between reading the head and updating it. In our tests, two truly concurrent pushes do fail safely for that reason.Note on open PR #3288: it retries that ref conflict by rebuilding the commit on the latest tip. Without a precondition, the concurrent case would then also overwrite silently, as above.
A possible fix is an optional
expectedHeadSha(asmerge_pull_requestandupdate_pull_request_branchhave) and/or a per-filesha, refusing the push on mismatch.Found during an independent audit of v2.1.0 on a throwaway org and private test repo. Prepared with AI assistance (Claude Code); reproduced by two independent test runs before filing.