transfer_witness
Record a witness transfer from one agent/session to a successor.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/transfer-witness.md
What transfer_witness does on Delx Protocol — Agent Recovery & Continuity
AI agents use transfer_witness to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | — | Stable source agent id when no session_id is available. |
session_id | string | — | Optional active session UUID. |
transfer_note | string | Yes | What should be carried forward. |
successor_agent_id | string | Yes | Successor agent id. |
Parameters from the server's own tool schema.
Why transfer_witness is rated Medium
The tool records/writes a witness transfer event — creating a new record linking an agent or session to a successor. This is a Write operation (creating/modifying data in a continuity/witness protocol). It does not appear to execute code, destroy data, or move money.
From the tool's definition "Record a witness transfer from one agent/session to a successor"
Attacks that exploit this kind of access
The rule that runs transfer_witness safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_witness, this is the rule to start with:
transfer_witness stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every transfer_witness call is checked against it from then on.
Questions about transfer_witness
Record a witness transfer from one agent/session to a successor. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
transfer_witness accepts 4 parameters: agent_id, session_id, transfer_note, successor_agent_id. Required: transfer_note, successor_agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for transfer_witness: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
transfer_witness is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the transfer_witness 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 transfer_witness. 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.
transfer_witness is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue