mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-11-18 14:08:21 +00:00
* 🗳️ 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 |
||
|---|---|---|
| .. | ||
| specs | ||
| src | ||
| .gitignore | ||
| babel.config.js | ||
| check_updates.sh | ||
| jest.config.js | ||
| package.json | ||
| tsconfig.build.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
| tsdown.config.mjs | ||