feat(advisor): Gate tools with read-only metadata#300
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Expose advisor tools from explicit read-only annotations instead of a static allowlist. Restrict advisor MCP discovery and dispatch to tools that opt into read-only use without destructive hints. Document the MCP annotation trust boundary and cover the production advisor tool set, including webFetch, with regression tests. Co-authored-by: GPT-5 Codex <codex@openai.com>
41b562c to
52cdd3b
Compare
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.
Advisor tool exposure now comes from tool annotations instead of the previous static allowlist. This lets the advisor receive any host-marked read-only tool while keeping recursive, mutating, and user-visible tools out of the advisor runtime.
MCP Read-Only Filtering
searchMcpTools and callMcpTool can now be constructed in read-only mode for the advisor. They expose only MCP tools with readOnlyHint: true and reject tools with destructiveHint: true.
Tool Metadata
Local read-only tools now declare MCP-style annotations, including webFetch, webSearch, file reads, system time, and read-only Slack surfaces. The advisor spec documents the trust boundary for remote MCP annotations.