Repository navigation
fix: drop environment variable write scope from MCP config - #8
Merged
Merged
Conversation
OpenAI's plugin review flagged create-account-environment-variable and update-account-environment-variable as soliciting secrets. The Checkly MCP server filters tools/list by granted scopes, so not requesting checkly:environment-variables:write removes both tools from the plugin.
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.
Why
OpenAI's plugin review flagged
create-account-environment-variableandupdate-account-environment-variableas soliciting secrets (passwords, API keys). Their policy: access credentials and authentication secrets cannot be solicited through public plugin tools.What
checkly:environment-variables:writefrom the scopes requested in.mcp.json.test/plugin-config.test.tsto assert the new scope list.The Checkly MCP server filters
tools/listby the token's granted scopes, so not requesting the write scope removes both tools from the plugin entirely. Read access to environment variables is unchanged.Not covered here
OpenAI's second finding (annotations on
trigger-checksandtrigger-root-cause-analysis) lives in the MCP server source and needs a separate change and deploy.