kg_scope_status
Check whether Knowledge Graph is in-scope for a given target.
This record as markdown: /tools/io-stablebaseline-sb/kg-scope-status.md
What kg_scope_status does on Stable Baseline
AI agents call kg_scope_status 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 |
|---|---|---|---|
folderId | string | — | |
projectId | string | — | |
documentId | string | — | |
workspaceId | string | — |
Parameters from the server's own tool schema.
Why kg_scope_status is rated Low
This tool queries the scope status of a Knowledge Graph without modifying, deleting, or executing external operations. It is a pure information-retrieval operation with no side effects, fitting the Read category. Severity is low because misuse would only expose organizational metadata about Knowledge Graph scope, not enable destructive or financial harm.
From the tool's definition Tool name 'kg_scope_status' and description 'Check whether Knowledge Graph is in-scope for a given target' indicate a query/lookup operation. The verb 'check' and lack of any modification language confirm this is a retrieval action.
Attacks that exploit this kind of access
The rule that runs kg_scope_status 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 kg_scope_status, this is the rule to start with:
kg_scope_status 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 kg_scope_status call is checked against it from then on.
Questions about kg_scope_status
Check whether Knowledge Graph is in-scope for a given target. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
kg_scope_status accepts 4 parameters: folderId, projectId, documentId, workspaceId. 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 kg_scope_status: 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.
kg_scope_status 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 kg_scope_status 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 kg_scope_status. 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.
kg_scope_status 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