// MCP TOOL REFERENCE

internal_transfer

ServerMcp Ap2
CategoryFinancial

WHAT IT DOES

What internal_transfer does on Mcp Ap2

AI agents use internal_transfer 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 internal_transfer needs a policy

This tool directly moves money between accounts without reversal capability once settled. It matches the Financial category definition ('moves money or commits financial obligations'). Given it settles instantly with no undo mechanism mentioned, operates within a fintech system, and explicitly transfers funds, this poses critical risk if an AI agent executes it with incorrect recipient or amount.

From the tool's definition Tool description explicitly states 'Book a transfer between two accounts' and 'moving funds across a fintech', indicating direct monetary movement.

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

POLICY

How to control internal_transfer

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 internal_transfer:

policy.json

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

Any call to internal_transfer 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 internal_transfer

What does the internal_transfer tool do? +

Book a transfer between two accounts both held on Matera (TED-interno / transferência interna). Settles instantly without touching SPI/Pix rails — no endToEndId, no DICT lookup. Use for moving funds across a fintech. 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 internal_transfer? +

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

What risk level is internal_transfer? +

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

Yes. Add a rate_limit block to the internal_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.

How do I block internal_transfer completely? +

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

What MCP server provides internal_transfer? +

internal_transfer 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.