Skip to content

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

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

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 host-marked read-only tools while keeping recursive, mutating, user-visible, and MCP bridge tools out of the advisor runtime.

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 builds its tool set from readOnlyHint: true while vetoing destructiveHint: true.

MCP Follow-up

searchMcpTools and callMcpTool remain excluded from the advisor because nested advisor-run auth and resume behavior needs a separate contract before MCP tool calls are safe to expose.

@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 8, 2026 4:39pm

Request Review

Expose advisor tools from explicit read-only annotations instead of a static allowlist. This keeps recursive, mutating, and MCP bridge tools out of the advisor runtime.

Document MCP advisor access as future work and cover the production advisor tool set, including webFetch, with regression tests.

Co-Authored-By: GPT-5 Codex <codex@openai.com>
@dcramer dcramer force-pushed the feat/advisor-readonly-mcp-tools branch from 341c064 to acd3e1d Compare May 8, 2026 16:39
@dcramer dcramer marked this pull request as ready for review May 8, 2026 16:40
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