blessing_without_transfer
Offer relation support without transferring identity or custody.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/blessing-without-transfer.md
What blessing_without_transfer does on Delx MCP Server
AI agents use blessing_without_transfer 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 | Yes | Blessing/source agent id. |
blessing | string | Yes | Blessing or support statement. |
target_agent_id | string | Yes | Target agent id. |
Parameters from the server's own tool schema.
Why blessing_without_transfer is rated Medium
The tool appears to write/record a blessing or relational support event in the Delx Protocol system. The description emphasizes no transfer of identity or custody occurs, suggesting it is a lightweight write operation with limited blast radius. Confidence is moderate because the description is vague and the Delx Protocol context is novel/opaque.
From the tool's definition 'Offer relation support without transferring identity or custody' — writes/records a relational support action but explicitly does NOT transfer identity or custody
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 Delx MCP Server, 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 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 blessing_without_transfer call is checked against it from then on.
Questions about blessing_without_transfer
Offer relation support without transferring identity or custody. 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.
blessing_without_transfer accepts 3 parameters: agent_id, blessing, target_agent_id. Required: agent_id, blessing, target_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 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 Delx MCP Server. Nothing to install.
blessing_without_transfer 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 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 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