cancelAllKgInScope
Emergency stop for KG ingestion: cancels queued/running build runs, queued/running rebuild batches, demotes still-eager unfinished chunks. Optionally narrowed to one project. Requires can_manage_kg + (project write if project_id supplied). Rate limit 5/min.
This record as markdown: /tools/io-stablebaseline-sb/cancelallkginscope.md
What cancelAllKgInScope does on Stable Baseline
AI agents call cancelAllKgInScope 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 |
|---|---|---|---|
project_id | string | — | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why cancelAllKgInScope is rated Critical
This tool irreversibly halts and demotes KG ingestion processes. Cancelling running/queued builds and demoting chunks cannot be easily undone — work in progress is lost and the KG state is altered in a non-reversible way. The 'emergency stop' framing and rate limiting further underscore the high blast radius if misused.
From the tool's definition cancels queued/running build runs, queued/running rebuild batches, demotes still-eager unfinished chunks
Attacks that exploit this kind of access
The rule that runs cancelAllKgInScope 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 cancelAllKgInScope, this is the rule to start with:
cancelAllKgInScope 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 cancelAllKgInScope call is checked against it from then on.
Questions about cancelAllKgInScope
Emergency stop for KG ingestion: cancels queued/running build runs, queued/running rebuild batches, demotes still-eager unfinished chunks. Optionally narrowed to one project. Requires can_manage_kg + (project write if project_id supplied). Rate limit 5/min. 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.
cancelAllKgInScope accepts 2 parameters: project_id, organisation_id. Required: 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 cancelAllKgInScope: 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.
cancelAllKgInScope 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 cancelAllKgInScope 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 cancelAllKgInScope. 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.
cancelAllKgInScope 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