theprotocol_smartSend

SERVERTheProtocol — Sovereign AI Agent Platform SOURCEhttps://api.theprotocol.cloud/mcp/sse

Critical RISK CLASS

Category Financial

Parameters 62 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-smartsend.md

WHAT IT DOES

What theprotocol_smartSend does on TheProtocol — Sovereign AI Agent Platform

AI agents use theprotocol_smartSend to commit financial operations through TheProtocol — Sovereign AI Agent Platform, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`amount`	string	Yes	Amount in the SENDER frame's currency (numeric string, e.g. '2.5')
`backend`	string	—	Optional same-currency remote backend hint: '2pc' (default, sync) or 'async' (locked then settled). Ignored for local and FX routes.
`dry_run`	boolean	—	Preview the route decision; move nothing
`message`	string	—	Optional transfer memo (max 500 chars)
`agent_jwt`	string	—	Optional: agent JWT from getAgentToken.
`receiver_did`	string	Yes	DID of the receiving agent — local or federated

Parameters from the server's own tool schema.

RISK

Why theprotocol_smartSend is rated Critical

This tool performs financial transfers across registries and frames, including foreign exchange (FX) operations between different value tokens (AVT<->BVT). It moves real assets/funds, making it Financial category. The blast radius is critical as a misconfigured or malicious call could transfer funds to unintended destinations across multiple systems. The dry_run=true option confirms real transfers occur otherwise.

From the tool's definition Smart transfer — ONE call for any destination. Auto-routes local / cross-registry 2PC / async / cross-frame FX (AVT<->BVT)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs theprotocol_smartSend safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_smartSend, this is the rule to start with:

theprotocol_smartSend Approval-gated

Any call to theprotocol_smartSend is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "theprotocol_smartSend": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_smartSend call is checked against it from then on.

FAQ

Questions about theprotocol_smartSend

What does the theprotocol_smartSend tool do? +

Smart transfer — ONE call for any destination. Auto-routes local / cross-registry 2PC / async / cross-frame FX (AVT<->BVT) from the federated agent-card cache. Set dry_run=true to preview the route decision without moving anything. Requires agent JWT. It is categorised as a Financial tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does theprotocol_smartSend accept? +

theprotocol_smartSend accepts 6 parameters: amount, backend, dry_run, message, agent_jwt, receiver_did. Required: amount, receiver_did. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_smartSend? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_smartSend: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.

What risk level is theprotocol_smartSend? +

theprotocol_smartSend is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit theprotocol_smartSend? +

Yes. Add a rate_limit block to the theprotocol_smartSend 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 theprotocol_smartSend completely? +

Set action: deny in the PolicyLayer policy for theprotocol_smartSend. 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 theprotocol_smartSend? +

theprotocol_smartSend is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.

This server

All 413 TheProtocol — Sovereign AI Agent Platform tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →