Skip to content

feat(advisor): Gate tools with read-only metadata#300

Draft
dcramer wants to merge 1 commit intomainfrom
feat/advisor-readonly-mcp-tools
Draft

feat(advisor): Gate tools with read-only metadata#300
dcramer wants to merge 1 commit intomainfrom
feat/advisor-readonly-mcp-tools

Conversation

@dcramer
Copy link
Copy Markdown
Member

@dcramer dcramer commented May 7, 2026

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.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
junior-docs Ready Ready Preview, Comment May 7, 2026 5:22am

Request Review

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant