New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

transfer_witness

Record a witness transfer from one agent/session to a successor.

SERVERDelx MCP Server SOURCEdelx-mcp-server
Medium RISK CLASS
Category Write
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about transfer_witness

What does the transfer_witness tool do? +

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.

What parameters does transfer_witness accept? +

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.

How do I enforce a policy on transfer_witness? +

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.

What risk level is transfer_witness? +

transfer_witness is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_witness? +

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.

How do I block transfer_witness completely? +

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.

What MCP server provides transfer_witness? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.