setKgDocumentScope
Toggle KG-scope override for a single document (on/off/inherit). Documents default to inheriting their folder/project gate. Requires can_manage_kg + document write. Rate limit 30/min.
This record as markdown: /tools/io-stablebaseline-sb/setkgdocumentscope.md
What setKgDocumentScope does on Stable Baseline
AI agents use setKgDocumentScope to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | Yes | |
document_id | string | Yes |
Parameters from the server's own tool schema.
Why setKgDocumentScope is rated Medium
This tool creates or modifies document scope settings within a Knowledge Graph, which is a configuration change. It is reversible (can toggle on/off/inherit), so it does not qualify as Destructive. While it affects access control and visibility settings, the core operation is writing/updating document metadata.
From the tool's definition Tool description states 'Toggle KG-scope override for a single document (on/off/inherit)' and requires 'document write' permission. The action modifies document scope settings, which is a reversible change to metadata/configuration.
Attacks that exploit this kind of access
The rule that runs setKgDocumentScope safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setKgDocumentScope, this is the rule to start with:
setKgDocumentScope stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every setKgDocumentScope call is checked against it from then on.
Questions about setKgDocumentScope
Toggle KG-scope override for a single document (on/off/inherit). Documents default to inheriting their folder/project gate. Requires can_manage_kg + document write. Rate limit 30/min. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
setKgDocumentScope accepts 2 parameters: state, document_id. Required: state, document_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for setKgDocumentScope: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Stable Baseline. Nothing to install.
setKgDocumentScope is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setKgDocumentScope rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for setKgDocumentScope. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
setKgDocumentScope is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue