blessing_without_transfer
Offer relation support without transferring identity or custody.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/blessing-without-transfer.md
What blessing_without_transfer does on Delx Mcp A2a
AI agents use blessing_without_transfer to commit financial operations through Delx Mcp A2a, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| 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 Critical
blessing_without_transfer moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
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 A2a, 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:
Any call to blessing_without_transfer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, 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 Financial tool in the Delx Mcp A2a MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
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 A2a 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 A2a. Nothing to install.
blessing_without_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
Across the catalogue