knowledge write tools: global-only semantic context - #1
Merged
rubywerman merged 1 commit intoSep 8, 2026
Merged
Conversation
node-scoped writes are gated off for GA (TK returns node_semantic_context_disabled), so drop targetNodeId/isGlobal from create + update. create always sends is_global:true; update only touches statements/name. reads (list/search) unchanged.
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
1 participant
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.
node-scoped semantic-context writes are gated off for GA — TK returns
node_semantic_context_disabled(403) for anytarget_node_idwrite, because node-scoped context is Tableau-owned and arrives via ingestion (confirmed w/ rami). the mcp create tool advertisedtargetNodeIdanyway, so agents picked it and got a bare 403. this locks the write tools to global to match.create-knowledge-semantic-contexts: droptargetNodeId/isGlobal, always sendis_global: trueupdate-knowledge-semantic-contexts: droptargetNodeId/isGlobal, only statements/namevalidateCreateAttachmentremoved;validateUpdatereduced to "at least one of statements/name"list/search) unchanged — ingested node context stays readable asSEMANTIC_CONTEXT_EXTERNALknowledgeApi.tsstill accepttarget_node_idfor when the gate flips post-GA; only the tool surface is lockedverification: 74/74 knowledge tests pass, eslint clean, tsc --noEmit clean.