Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Gap]: Document per-group tool restrictions (Tools tab, Sync tools, Choose tools)

未关闭 适合新手
  • 哪里不对？
#1,285 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
84/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
documentation

调研方向

先查看 connector-policies.mdx 和 connectors.mdx，然后阅读 support-connector-access.mdx 中现有的“Tool choices”部分，了解相关的用户指引。说明连接器同步、各组的工具选择、限制对新工具和用户选择的影响、拒绝何时生效，以及明确说明的限制；从 connectors.mdx 添加一条简短指引。管理员能够按照文档限制某个组可用的工具，并了解文档中说明的注意事项，即视为完成。

由索引模型根据 Issue 内容生成。

描述

documentation enhancement needs-triage
What needs documentation?

Admin control over which tools each group can use on a connector. The docs currently only describe users turning tools off for themselves (support-connector-access.mdx, "Tool choices"). The admin side is missing:

  • The connector Tools tab and Sync tools. A connector's tool list is empty until an admin syncs it. For connectors that act as each user (upstream identity provider, token exchange, OBO), the admin must sign in to the connector first; the tab shows "Sign in required to sync". After a sync, the tab lists each tool with its type (Read-only, Destructive, Write) and its access across groups (for example "Allowed, 1 of 1 group" or "Blocked, 0 of 1 group").
  • Choose tools per group (connector → Access → group's actions menu → Choose tools). Tools are grouped by category, and the admin unticks tools or whole categories.
  • The two states and what they mean for new tools:
    • "New tools are allowed automatically": the group has no restriction.
    • "New tools are blocked for this group until you allow them": the group has a restriction.
    • After a change, new tools discovered on the connector are blocked for that group.
  • How group restrictions combine with users' own tool choices. The group restriction is a ceiling; users can only narrow further.
  • When it takes effect. The next tool call is refused. The client can still list the tool until its tool list refreshes.
  • Known limitations, until they're fixed:
    • Re-ticking every tool doesn't return a group to "allowed automatically" (stacklok/stacklok-enterprise-platform#5759); revoke and re-grant the group to reset it.
    • Refused calls don't appear in Activity (stacklok/stacklok-enterprise-platform#3901).
  • Connector descriptions (small, related): connectors added with Discover in Kubernetes keep "Auto-published from MCPServer …" as their description, and users see it in their catalog. Advise setting a description after adding them, until stacklok/stacklok-enterprise-platform#5761 changes the default.
Context and references
  • Console guidance for never-synced connectors: stacklok/stacklok-enterprise-platform#5490
  • Connector-level default tool access (API): stacklok/stacklok-enterprise-platform#5302
  • Earlier platform work (all closed): stacklok/stacklok-enterprise-platform#4371, stacklok/stacklok-enterprise-platform#4372, stacklok/stacklok-enterprise-platform#4375, stacklok/stacklok-enterprise-platform#4376

Suggested home: a new "Restrict tools for a group" section in connector-policies.mdx, with a short pointer from connectors.mdx.

Use case

As a platform admin, I want to grant a connector to a group but keep its destructive or high-risk tools away from that group, without asking every user to turn those tools off themselves.

Additional context

Exercised on the demo cluster, October 27, 2026: synced OSV, blocked two read-only tools for All FTE, and confirmed the next calls from LibreChat failed.

Fully or partially written by an AI agent.

主要语言
JavaScript
星标
4
派生
4
平均合并
19 小时 20 分钟
30 天内合并 PR
85

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

stacklok/docs-website 的其他 Issue

查看 stacklok/docs-website 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。