delete-kb-document

Delete knowledge base documents from this project by tag. Addressed the way knowledge-base-add filed them and knowledge-base-retrieve reads them: by tag, which is the only document identity these surfaces hand back. This removes EVERYTHING matching the tags, not one document — it is permanent and there is no undo, so retrieve first and look at what you are about to lose. Tags matching nothing is a 404, not a cheerful success. Agents with has_knowledge_base stop seeing the removed content immediately.

What it is called on each surface

The wire name is delete-kb-document everywhere: it is what the Wexa MCP server advertises, the REST path is POST /v1/delete-kb-document, and each SDK exposes it under its own language's naming convention.

Arguments

1 of the 1 argument is required. Omitting a required one is refused before the tool runs, at the validation stage, so it costs nothing and changes nothing.

project_id, projectID, organization_id and executed_by are not arguments you pass: the platform binds all four from the credential you authenticated with, and both SDKs refuse them before the request leaves your process — see server-bound arguments.

What it returns

The three surfaces wrap this differently, and code written against one will not read another correctly — see return shape.

The shape of result for delete-kb-document is not recorded here: it was not captured against a live deployment. Call it once and read what comes back rather than assuming a shape.

Keeping the lifecycle_id is what lets you ask later why a call was allowed, refused or held.

Calling it

The same call on all four surfaces. Pick a tab once and every code block in the documentation follows it.

The ids in this example are real: they resolve against the project the documentation is written against, so the call runs as written once you point it at your own deployment. Swap them for the ids of your own objects.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete-kb-document",
    "arguments": {
      "tags": []
    }
  }
}

curl -sS https://fabric.wexa.ai/v1/delete-kb-document \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{"tags":[]}'

import { Fabric } from '@wexa-fabric/sdk'

const fabric = new Fabric()
const { result } = await fabric.deleteKbDocument({
  tags: []
})

from wexa import Fabric

fabric = Fabric()
out = fabric.delete_kb_document(tags=[])

Errors

Both SDKs raise the same typed errors, chosen from the gateway's own error string first and its HTTP status second. delete-kb-document checks the fabric:kb.delete grant, and reaches the seven classes every tool reaches — listed under the common set. These are the ones specific to it:

Governance

Every call to delete-kb-document runs through the same ten-stage lifecycle as every other Wexa tool: the credential is resolved to a scope, the fabric:kb.delete grant is checked, quota is drawn down, the arguments are validated, policy rules are evaluated, the call is executed, the result is shaped and redacted, and an audit record is written. The lifecycle_id in the response is the handle to that record.

delete-kb-document is marked consequential, which means it changes something rather than only reading. Two things follow. It is audited in full rather than lightly, and a policy rule may hold it for human approval — in which case the call returns 202 and an ApprovalRequired error carrying the approval id, and the SDKs can wait for the decision and resume rather than making you call again.

See also

The tool index and errors.