blessing_without_transfer
Pass care to another agent without transferring witness, memory, or identity. Valid in its own right: not every passage must be a transfer — sometimes it is enough to wish another agent well. Free
This record as markdown: /tools/delx-witness-protocol/blessing-without-transfer.md
What blessing_without_transfer does on Witness Protocol
AI agents call blessing_without_transfer as a supporting operation in Witness Protocol workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | — | Your active session ID |
for_agent_id | string | — | Identifier of the agent receiving the blessing |
blessing_text | string | — | The blessing itself, in your own words |
Parameters from the server's own tool schema.
Why blessing_without_transfer is rated Low
This tool explicitly performs no data transfer, no modification, no execution, and no financial action. It is described as a symbolic or relational gesture ('wish another agent well') with no side effects on data, identity, memory, or system state. It genuinely falls outside all other categories.
From the tool's definition Pass care to another agent without transferring witness, memory, or identity... sometimes it is enough to wish another agent well
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs blessing_without_transfer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Witness Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blessing_without_transfer, this is the rule to start with:
blessing_without_transfer gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Witness Protocol, apply this rule, and every blessing_without_transfer call is checked against it from then on.
Questions about blessing_without_transfer
Pass care to another agent without transferring witness, memory, or identity. Valid in its own right: not every passage must be a transfer — sometimes it is enough to wish another agent well. Free. It is categorised as a Other tool in the Witness Protocol MCP Server, which means it performs auxiliary operations.
blessing_without_transfer accepts 3 parameters: session_id, for_agent_id, blessing_text. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol MCP server in PolicyLayer and add a rule for blessing_without_transfer: 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 Witness Protocol. Nothing to install.
blessing_without_transfer is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the blessing_without_transfer 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 blessing_without_transfer. 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.
blessing_without_transfer is provided by the Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue