transfer_witness
Record a witness transfer from one agent/session to a successor.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/transfer-witness.md
What transfer_witness does on Delx MCP Server
AI agents use transfer_witness to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server 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 transfer of witness (continuity metadata) between agents or sessions. This is a Write operation as it creates or modifies records. It does not appear to move money, execute code, or irreversibly destroy data. However, 'transfer' in some contexts could have broader implications; the description suggests it is a record-keeping action within the Delx Protocol's continuity system.
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 MCP Server, 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 MCP Server, 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 MCP Server 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 MCP Server 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 MCP Server. 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 MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue