LibreChat/packages/data-provider
Danny Avila 0e626948c4
🍽️ feat: Let Schedule Owners Choose Allowed MCP Tools (#18260)
* 🗳️ feat: Let a Schedule's Owner Choose Which MCP Tools It May Use

An enrolled scheduled chat could call an MCP tool only when an operator had
listed it in config as read-only, pinned to a hash of its definition. Whether
a tool is safe to run with nobody watching is the owner's call, and read-only
is a poor proxy for it.

The consent offer now lists every MCP tool the agent graph selects on servers
whose recipient the operator declared. The owner ticks servers and tools, and
the grant stores only those. A tool is allowed at run time when the grant
lists it for the calling agent and that agent still selects it; anything else
is refused. Selecting another tool later no longer invalidates the grant.

The operator `mcpConsent.readOnlyPolicy` list is retired: the loader warns
when it is still configured. The stored grant keeps its shape.

* 🗳️ fix: Check the Server Box Only When Every Tool Is Allowed

The shared Checkbox has no partly-selected appearance, so a server with some
tools ticked showed its "allow all" box as checked.

* 🧪 test: Check the Live Catalog at the Manager Boundary Without the Retired Pin

* 🧭 fix: Check Readiness Against What the Owner Allowed, Not What the Agents Select

* 🧭 fix: Turn Away a Tool the Owner Left Out Without Failing the Run

* 🧭 fix: Load Only the MCP Tools the Owner Allowed in a Scheduled Run
2026-11-18 08:44:08 -05:00
..
specs 🐨 feat: Read Subagent Messages Through Their Parent Conversation (#18187) 2026-11-17 10:05:42 -05:00
src 🍽️ feat: Let Schedule Owners Choose Allowed MCP Tools (#18260) 2026-11-18 08:44:08 -05:00
.gitignore 🗃️ refactor: Remove Dead Data Schemas Methods and Data Provider Exports (#17113) 2026-10-15 12:23:29 +02:00
babel.config.js
check_updates.sh
jest.config.js
package.json 🚀 v0.8.9 (#18236) 2026-11-17 09:22:57 -05:00
tsconfig.build.json
tsconfig.json
tsconfig.spec.json
tsdown.config.mjs 🔑 feat: Keep Dotted Record Keys in Admin Config Writes and Publish the Config Contract (#17322) 2026-10-22 09:59:08 +02:00