theprotocol_transferTokens
Transfer units to another agent on this registry. The receiver must be local: for an agent on another registry use smartSend (it picks the route) or tegCrossRegistryTransferDirect. The registry's transfer fee applies. Pass idempotency_key and reuse it on a retry. Requires agent JWT authentication.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-transfertokens.md
What theprotocol_transferTokens does on TheProtocol — Sovereign AI Agent Platform
AI agents use theprotocol_transferTokens 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 to transfer, in the frame's units (numeric string, e.g. '10.5') |
message | string | — | Optional transfer memo (max 256 chars) |
agent_jwt | string | — | Optional: agent JWT from getAgentToken. |
recipient_did | string | Yes | DID of the receiving agent |
idempotency_key | string | — | reuse it on a retry: the route answers the first result again for 24 h instead of moving units twice (namespaced to the caller before it is sent) |
Parameters from the server's own tool schema.
Why theprotocol_transferTokens is rated Critical
theprotocol_transferTokens 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 theprotocol_transferTokens 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_transferTokens, this is the rule to start with:
Any call to theprotocol_transferTokens is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_transferTokens call is checked against it from then on.
Questions about theprotocol_transferTokens
Transfer units to another agent on this registry. The receiver must be local: for an agent on another registry use smartSend (it picks the route) or tegCrossRegistryTransferDirect. The registry's transfer fee applies. Pass idempotency_key and reuse it on a retry. Requires agent JWT authentication. 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.
theprotocol_transferTokens accepts 5 parameters: amount, message, agent_jwt, recipient_did, idempotency_key. Required: amount, recipient_did. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_transferTokens: 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.
theprotocol_transferTokens 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 theprotocol_transferTokens 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 theprotocol_transferTokens. 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.
theprotocol_transferTokens 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.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
This server
Across the catalogue