applyKgScopeChange
Apply a previously previewed KG scope change. Atomically writes kg_scope rows and dispatches a re-ingest batch (batch_id = token). Databases and tables in the token are applied in the same step: their name keys are built from their own fields (no AI), and switching one off removes them. Idempoten...
This record as markdown: /tools/io-stablebaseline-sb/applykgscopechange.md
What applyKgScopeChange does on Stable Baseline
AI agents use applyKgScopeChange 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 |
|---|---|---|---|
confirmation_token | string | Yes |
Parameters from the server's own tool schema.
Why applyKgScopeChange is rated Medium
An AI agent can call applyKgScopeChange faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs applyKgScopeChange 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 applyKgScopeChange, this is the rule to start with:
applyKgScopeChange 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 applyKgScopeChange call is checked against it from then on.
Questions about applyKgScopeChange
Apply a previously previewed KG scope change. Atomically writes kg_scope rows and dispatches a re-ingest batch (batch_id = token). Databases and tables in the token are applied in the same step: their name keys are built from their own fields (no AI), and switching one off removes them. Idempotent. Rate limit 5/h. 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.
applyKgScopeChange accepts 1 parameter: confirmation_token. Required: confirmation_token. 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 applyKgScopeChange: 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.
applyKgScopeChange 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 applyKgScopeChange 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 applyKgScopeChange. 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.
applyKgScopeChange 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