Privent icon

Privent

Privent DLP: session-scoped tokenization, detokenization, risk scoring, audit events and agent handoffs for AI agent workflows.

Actions6

Handoff → Record

AI-generated

Summary

Records an agent handoff in Privent’s Trust Map, linking a source agent and session to either another in-organization agent or an external sink. Use API Key authentication and supply the source session and agent; choose a target kind and provide its corresponding identifier. The operation sends an audit event to the Privent backend and returns the input item with the recorded handoff details.

Inputs

  • Authentication — Choose API Key authentication to record handoffs. Tokenless and Local modes do not expose the handoff fields.
  • Session ID (required) — Session ID from the upstream Privent Session node; identifies the source side of the handoff.
  • Trace ID — Correlation ID from the upstream session. If omitted, a fresh ID is generated when no session node supplies one.
  • From Agent Name (required) — Canonical name of the source agent, usually from the upstream Privent Session node.
  • Target Kind — Select Agent (In-Org) or External Sink.
  • Target Agent Name (required) — For an in-organization target, provide its canonical agent name, which should match the name emitted by the downstream Privent Session node.
  • External Sink ID (required) — For an external target, provide an opaque identifier such as a webhook URL hash or partner ID.
  • Reason — Categorize the handoff as Delegation, Other, Subgraph Call, Tool Invocation, or Webhook Trigger; defaults to Delegation.
  • Payload Token Count — Optional nonnegative token volume hint for Trust Map blast-radius calculations. A value of 0 is omitted.

Output shape

One output item per input item, with the input JSON preserved and handoff result fields added.

The operation records the handoff through the Privent backend; it requires API Key authentication and a valid source session and target.

Links

Discussion