Limit export MCP pre-approval to its five required read tools - #22
Open
manuelconcari-ai wants to merge 1 commit into
Open
manuelconcari-ai wants to merge 1 commit into
manuelconcari-ai wants to merge 1 commit into
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
1 participant
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.
The export prerequisite recommends a user-wide grant for every tool exposed by the HackenProof MCP server, although the published workflow requires only five reads. That grant can also match the repository's triage write tools.
Replace both wildcard recommendations with the five exact tool names, in optional project-local settings or in user settings for someone who wants one grant across projects. Explain how to remove an earlier broad grant from every settings file that supplies it: permission lists merge across files, so adding narrower entries does not revoke the wildcard. Preserve the export workflow and distinguish MCP approval from local file permissions and the triage skills' confirmation requirements.
Validation: checked the full export skill and Markdown template, including program discovery, pagination, comments and attachment handling. The patch changes only the prerequisite section of one file; the example JSON parses and contains exactly the five MCP reads required by that workflow. The patch applies to main at 60d8813.
This narrows a documented permission recommendation. No connected MCP server or Claude Code runtime was exercised, and no deployed permission bypass or runtime enforcement claim is made.