Mark read-only Docker Hub tools with readOnlyHint#80
Open
RomanOstr wants to merge 1 commit into
Open
Conversation
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
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.
Summary
readOnlyHint: trueto read-only Docker Hub MCP toolstools.jsonWhy
Several Docker Hub tools are read-only, but they are currently published without
readOnlyHint. MCP clients can then classify them as potentially mutating and prompt more aggressively than needed.This patch marks the non-mutating account, repository, tag, hardened-image, and search tools as read-only.
Scope
This PR intentionally excludes fork-specific repo maintenance changes such as CI hardening, CODEOWNERS, release workflow changes, and Docker Hub publishing setup. It keeps the upstream proposal limited to the MCP metadata fix itself.
Validation
npm run lintpassed locally on WindowsNote: local
npm run buildandnpm run list-tools:checkhit a Windows-specific Node heap exhaustion in this environment, so I am not claiming those as local passes.