triggerKgRebuild
Apply a previously previewed KG rebuild. Dispatches the build batch via kg-rebuild and returns batch_id. Rate limit 5/h.
This record as markdown: /tools/io-stablebaseline-sb/triggerkgrebuild.md
What triggerKgRebuild does on Stable Baseline
AI agents invoke triggerKgRebuild to trigger actions in Stable Baseline. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirmation_token | string | Yes |
Parameters from the server's own tool schema.
Why triggerKgRebuild is rated High
This tool triggers execution of a Knowledge Graph rebuild process, which is an external operation whose effects depend on the state of the KG and rebuild parameters. It dispatches work to an external system (kg-rebuild) and initiates a process that cannot be trivially undone mid-execution, though it is not strictly destructive since it rebuilds rather than deletes.
From the tool's definition Tool name 'triggerKgRebuild' and description 'Apply a previously previewed KG rebuild. Dispatches the build batch via kg-rebuild and returns batch_id.' indicate execution of a background rebuild operation with external system dispatch.
Attacks that exploit this kind of access
The rule that runs triggerKgRebuild 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 triggerKgRebuild, this is the rule to start with:
triggerKgRebuild stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 triggerKgRebuild call is checked against it from then on.
Questions about triggerKgRebuild
Apply a previously previewed KG rebuild. Dispatches the build batch via kg-rebuild and returns batch_id. Rate limit 5/h. It is categorised as a Execute tool in the Stable Baseline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
triggerKgRebuild accepts 1 parameter: confirmation_token. Required: confirmation_token. 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 triggerKgRebuild: 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.
triggerKgRebuild is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the triggerKgRebuild 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 triggerKgRebuild. 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.
triggerKgRebuild 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