resetDocumentInBrain
Wipe + re-ingest a single document in the KG. Drops chunks/mentions/entities, clears pending lazy-extraction, and enqueues a fresh extract pass. Requires can_manage_kg + document write. Rate limit 30/min.
This record as markdown: /tools/io-stablebaseline-sb/resetdocumentinbrain.md
What resetDocumentInBrain does on Stable Baseline
AI agents call resetDocumentInBrain 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 |
|---|---|---|---|
document_id | string | Yes |
Parameters from the server's own tool schema.
Why resetDocumentInBrain is rated Critical
The tool's primary action is to drop/wipe existing document knowledge graph artifacts. While the document itself may persist, the destructive operation on extracted knowledge components (chunks, mentions, entities) that cannot be recovered from this tool alone places it in the Destructive category.
From the tool's definition 'Wipe + re-ingest a single document in the KG. Drops chunks/mentions/entities, clears pending lazy-extraction' — the tool irreversibly deletes indexed document data (chunks, mentions, entities) before reingest.
Attacks that exploit this kind of access
The rule that runs resetDocumentInBrain 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 resetDocumentInBrain, this is the rule to start with:
resetDocumentInBrain 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 resetDocumentInBrain call is checked against it from then on.
Questions about resetDocumentInBrain
Wipe + re-ingest a single document in the KG. Drops chunks/mentions/entities, clears pending lazy-extraction, and enqueues a fresh extract pass. Requires can_manage_kg + document write. Rate limit 30/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.
resetDocumentInBrain accepts 1 parameter: document_id. Required: document_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 resetDocumentInBrain: 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.
resetDocumentInBrain 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 resetDocumentInBrain 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 resetDocumentInBrain. 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.
resetDocumentInBrain 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