// MCP TOOL REFERENCE

transfer_between_wallets

ServerMcp Ap2
CategoryFinancial

How to control transfer_between_wallets ↓

WHAT IT DOES

What transfer_between_wallets does on Mcp Ap2

AI agents use transfer_between_wallets to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.

THE RISK

Critical Risk

Why transfer_between_wallets needs a policy

This tool directly moves funds between wallets, which constitutes a financial transaction. The severity is critical because: (1) it involves irreversible movement of money; (2) misuse could result in unauthorized transfers, theft, or fraud; (3) it operates on financial accounts with real monetary value; (4) the impact is immediate and affects financial obligations.

From the tool's definition Tool transfers funds between Rapyd ewallets (source_ewallet → destination_ewallet); explicitly handles marketplace settlement, creator payouts, and internal rebalancing. This is direct movement of money between financial accounts.

Documented attack patterns abuse exactly the kind of access transfer_between_wallets gives an agent:

POLICY

How to control transfer_between_wallets

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for transfer_between_wallets:

policy.json

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

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

Create a free account and register Mcp Ap2 — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Ap2 tools

Financial authorize_transaction Authorize a transaction (reserve funds without capturing) via Braintree GraphQL authorizeP Financial block_card Block a card temporarily (reversible). Use for lost-card or fraud-suspected flows. Card st Financial cancel_bill Cancel a pending bill Financial cancel_collection Cancel a scheduled collection request Financial cancel_credit Cancel an authorized-but-uncaptured credit payment. Financial cancel_debit Cancel a debit-card payment by Getnet payment_id. Financial cancel_invoice Cancel/void an authorized invoice (FECancel — limited to certain types/conditions) Financial cancel_order Cancel an order, optionally restocking and refunding

All 1300 Mcp Ap2 tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in Mcp Ap2 → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about transfer_between_wallets

What does the transfer_between_wallets tool do? +

Move funds between two Rapyd ewallets (source_ewallet → destination_ewallet). Used for marketplace settlement (buyer wallet → seller wallet), creator payouts, internal rebalancing. Requires transfer acceptance on the destination side in some flows. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_between_wallets? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for transfer_between_wallets: 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 Mcp Ap2. Nothing to install.

What risk level is transfer_between_wallets? +

transfer_between_wallets 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 transfer_between_wallets? +

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

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

transfer_between_wallets is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.