delete-context

Delete a node from this project's context graph, together with its relationships. Address it exactly as you wrote it with save-context: {label, key, value}. Deleting is permanent and there is no undo, so this reports how many nodes matched — if it matched nothing you get an error, not a cheerful success. Platform-managed labels cannot be deleted through this tool. query-context refuses DELETE/DETACH on purpose; this is the only delete path.

What it is called on each surface

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

Surface	Name
Wexa MCP server	`delete-context`
REST API	`POST /v1/delete-context`
TypeScript SDK	`fabric.deleteContext()`
Python SDK	`fabric.delete_context()`

Arguments

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

Argument	Type	Required	Notes
`key`	string	Required	The merge-key property name you wrote it with, e.g. "id". Required.
`label`	string	Required	The node's label, e.g. "Customer". Required.
`value`	any	Required	The merge-key value identifying the node. Required.

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.

A real response, captured from a live call to delete-context:

{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000213\",\"result\":{\"deleted\":1,\"element_ids\":[\"360525967589900288\"],\"label\":\"FixtureCustomer\",\"relationships\":\"detached with the node(s)\"}}"
    }
  ],
  "isError": false
}

{
  "lifecycle_id": "qlc_000213",
  "result": {
    "deleted": 1,
    "element_ids": [
      "360525967589900288"
    ],
    "label": "FixtureCustomer",
    "relationships": "detached with the node(s)"
  }
}

// the object you get back IS the result — there is no `.result` to read
{
  deleted: 1,
  element_ids: [ '360525967589900288' ],
  label: 'FixtureCustomer',
  relationships: 'detached with the node(s)'
}

// The TS SDK names these camelCase — lifecycleId, traceId — where Python uses
// lifecycle_id and trace_id. Both are non-enumerable: readable, but omitted by
// Object.keys() and JSON.stringify(). `result.lifecycleId` here is undefined.
result.lifecycleId // 'qlc_000213'

# a dict subclass; `result` is already unwrapped
{
 "deleted": 1,
 "element_ids": [
  "360525967589900288"
 ],
 "label": "FixtureCustomer",
 "relationships": "detached with the node(s)"
}

out.lifecycle_id  # 'qlc_000213' — an attribute, not a key

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, and resolve against the project the documentation is written against. Swap them for your own. A value in angle brackets is one only you can supply, and the platform refuses a literal <...>.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete-context",
    "arguments": {
      "key": "<key>",
      "label": "<label>",
      "value": "<value>"
    }
  }
}

curl -sS https://fabric.wexa.ai/v1/delete-context \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{"key":"<key>","label":"<label>","value":"<value>"}'

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

const fabric = new Fabric()
const { result } = await fabric.deleteContext({
  key: "<key>",
  label: "<label>",
  value: "<value>"
})

from wexa import Fabric

fabric = Fabric()
out = fabric.delete_context(key="<key>", label="<label>", value="<value>")

Errors

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

Error	Status	Raised when
`ApprovalRequired`	202	A policy held this call for a person to approve. The error carries the approval id; see below.
`ConfigurationError`	5xx	`delete-context` is not available to you. Retrying will not help.

Governance

Every call to delete-context runs through the same ten-stage lifecycle as every other Wexa tool: the credential is resolved to a scope, the fabric:ontology.write 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-context 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.