getKgScopeTree
List every kg_scope row for the caller's organisation, optionally narrowed to a workspace or project subtree. Each row carries scope_type, scope_id, state (on|off|inherit), settings, and is augmented with scope_name + parent_id for tree rendering. Capped at 500 rows.
This record as markdown: /tools/io-stablebaseline-sb/getkgscopetree.md
What getKgScopeTree does on Stable Baseline
AI agents call getKgScopeTree 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 |
|---|---|---|---|
project_id | string | — | Optional — narrow the result to this project's subtree |
workspace_id | string | — | Optional — narrow the result to this workspace's subtree |
organisation_id | string | Yes | Must match the credential's org |
Parameters from the server's own tool schema.
Why getKgScopeTree is rated Low
getKgScopeTree retrieves and enumerates Knowledge Graph scope configuration data for organizational visibility and tree rendering. It performs no mutations, deletions, or state changes. Even with broad access to organizational scope data, the blast radius is limited to information disclosure; misuse would not corrupt data, trigger external actions, or cause irreversible harm. This is a classic Read operation.
From the tool's definition Tool description states 'List every kg_scope row' with retrieval of scope metadata (scope_type, scope_id, state, settings, scope_name, parent_id).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs getKgScopeTree 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 getKgScopeTree, this is the rule to start with:
getKgScopeTree 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 getKgScopeTree call is checked against it from then on.
Questions about getKgScopeTree
List every kg_scope row for the caller's organisation, optionally narrowed to a workspace or project subtree. Each row carries scope_type, scope_id, state (on|off|inherit), settings, and is augmented with scope_name + parent_id for tree rendering. Capped at 500 rows. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getKgScopeTree accepts 3 parameters: project_id, workspace_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 getKgScopeTree: 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.
getKgScopeTree 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 getKgScopeTree 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 getKgScopeTree. 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.
getKgScopeTree 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