⚠️ 验证
🎯 解决方案描述
I'd like to be able to set up an MCP server, but then disable some of the tools it provides.
Here is an example config:
name: dav
tenant: default
routers:
- server: dav
prefix: /gateway/dav
servers: []
tools: []
prompts: []
mcpServers:
- type: streamable-http
name: dav
env:
Authorization: Bearer dummy
url: https://dav.mydomain.com/mcp
policy: onDemand
preinstalled: false
For this example, I am using https://github.com/PhilflowIO/dav-mcp
I can configure this MCP server in Unla, it essentially acts as a passthrough:
This MCP server exposes MANY tools, however I would like, on the Unla side, to "disable" some of them, such that I can either "blocklist" or "allowlist" an explicit set of tools that will passthrough.
📋 使用场景
This means in my OpenCode, I can add Unla's gateway, and it will see a subset of the upstream tools. This saves context and prevents OpenCode from being able to call tools I don't want enabled. Doing this on the Unla side means I don't have to individually configure multiple different OpenCode installations.
⚖️ 复杂性与风险
No response
🔗 外部依赖
No response
📘 附加上下文
No response
🎯 解决方案描述
I'd like to be able to set up an MCP server, but then disable some of the tools it provides.
Here is an example config:
For this example, I am using https://github.com/PhilflowIO/dav-mcp
I can configure this MCP server in Unla, it essentially acts as a passthrough:
This MCP server exposes MANY tools, however I would like, on the Unla side, to "disable" some of them, such that I can either "blocklist" or "allowlist" an explicit set of tools that will passthrough.
📋 使用场景
This means in my OpenCode, I can add Unla's gateway, and it will see a subset of the upstream tools. This saves context and prevents OpenCode from being able to call tools I don't want enabled. Doing this on the Unla side means I don't have to individually configure multiple different OpenCode installations.
⚖️ 复杂性与风险
No response
🔗 外部依赖
No response
📘 附加上下文
No response