previewKgScopeChange
Preview the credit cost, source counts, and ETA of including or excluding KG scope rows. Returns confirmation_token (10-min TTL) plus delta of newly-in-scope vs newly-out-of-scope sources. Databases and tables are off by default and are switched on here too: scope_type database or table, a table ...
This record as markdown: /tools/io-stablebaseline-sb/previewkgscopechange.md
What previewKgScopeChange does on Stable Baseline
AI agents call previewKgScopeChange to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
changes | array | Yes | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why previewKgScopeChange is rated Critical
An AI agent that decides to call previewKgScopeChange doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Stable Baseline is gone. There is no undo for destructive operations.
Risk signalsHigh parameter count (18 properties)
Attacks that exploit this kind of access
The rule that runs previewKgScopeChange 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 previewKgScopeChange, this is the rule to start with:
previewKgScopeChange is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every previewKgScopeChange call is checked against it from then on.
Questions about previewKgScopeChange
Preview the credit cost, source counts, and ETA of including or excluding KG scope rows. Returns confirmation_token (10-min TTL) plus delta of newly-in-scope vs newly-out-of-scope sources. Databases and tables are off by default and are switched on here too: scope_type database or table, a table with its field choices in settings. Their estimate comes back as records: rows and name keys to build or remove, storage against the brain's allowance, the time until ready, and no credits. A table that agents fill from messages that stay out of the brain (records.needs_confirm) needs the person's agreement, then confirm_messages: true on its change. Owners and admins only. Rate limit 20/h. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
previewKgScopeChange accepts 2 parameters: changes, organisation_id. Required: changes, organisation_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 previewKgScopeChange: 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.
previewKgScopeChange is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the previewKgScopeChange 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 previewKgScopeChange. 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.
previewKgScopeChange 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.
Across the catalogue