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. Rate limit 20/h.
This record as markdown: /tools/io-stablebaseline-sb/previewkgscopechange.md
What previewKgScopeChange does on Stable Baseline
AI agents call previewKgScopeChange to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
changes | array | Yes | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why previewKgScopeChange is rated Low
This tool only previews/calculates what a scope change would cost and affect, returning a confirmation token and delta information without actually applying any changes. The actual application is handled by 'applyKgScopeChange'. It is a read/query operation with no side effects.
From the tool's definition Preview the credit cost, source counts, and ETA... Returns confirmation_token plus delta of newly-in-scope vs newly-out-of-scope sources
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 read-only, so it stays allowed. 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 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. Rate limit 20/h. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
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 Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
This server
Across the catalogue