| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The label_write delete method removes labels repository-wide but the tool only advertised ReadOnlyHint:false. Set DestructiveHint:true so MCP clients can warn before destructive label deletions, matching projects_write. Fixes github#2723
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c999f008-c5da-4948-a6fd-e221ded750df
| Back | FazBrowse Home | New Git URL |
Summary
Add DestructiveHint: true to the label_write tool annotations so MCP clients can surface appropriate warnings before repository-wide label deletions.
Motivation
The label_write tool supports create, update, and delete methods. The delete method permanently removes a label and all of its associations from every issue and PR in the repository. The tool currently only sets ReadOnlyHint: false, giving clients no destructive-operation signal.
Deleting a label removes it repository-wide from all issues and pull requests (GitHub API permanent delete).
Fixes #2723
Rationale
label_write is a multi-method tool (create / update / delete). MCP tool annotations are tool-scoped (no per-method hints), so we mark the entire tool destructiveHint: true when any method is destructive—matching projects_write and discussion_comment_write.
Changes
Tests
Impact
Hosts/clients may show destructive-operation warnings for all label_write calls, including create/update. This is intentional conservative labeling.