feat(kap-server): expose per-tool active state in GET /api/v1/tools - #2005
Merged
Conversation
🦋 Changeset detectedLatest commit: 2aeeb07 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Signed-off-by: 7Sageer <7sageer@djwcb.cn>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
No tracking issue — follow-up to #1735.
Problem
#1735 introduced three tool gates (profile
tools/disallowedTools, the global[tools]config, and the sessiondisabled_toolsdenylist) and let clients write the session denylist on prompt submission — but gave them no public way to read back the effective result. A client that setsdisabled_toolscannot discover valid tool names or confirm which tools ended up active; the only gate-aware listing lived on the dev-only/api/v1/debugdispatcher.What changed
GET /api/v1/toolsnow reports anactiveflag per tool — the effective availability under the composed tool policy (bound profile ∩ global[tools]config ∩ session denylist), computed with the sameIAgentToolPolicyService.isToolActivethe engine RPCgetToolsuses, so both surfaces agree.ToolDescriptor.activeis optional in both the kap-server-local and the shared@moonshot-ai/protocolschema: additive wire change, so old clients and the legacy v1 projection (no gate concept) are unaffected.active: true).active: trueon the existing projection case; a new case asserting a session-denied tool wires out asactive: falsewhile others staytrue; schema round-trip in@moonshot-ai/protocol.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.