Africa Payments MCP

32 tools. 16 can modify or destroy data without limits.

14 destructive tools with no built-in limits. Policy required.

Last updated:

16 can modify or destroy data
16 read-only
32 tools total

Community server · catalogue entry verified 03/07/2026

How to control Africa Payments MCP ↓

What Africa Payments MCP exposes to your agents

Read (16) Write / Execute (2) Destructive / Financial (14)
Critical Risk

The most dangerous Africa Payments MCP tools

16 of Africa Payments MCP's 32 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Africa Payments MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Africa Payments MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "b2c_transfer": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "c2b_register": {
    "limits": [
      {
        "counter": "c2b_register_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "calculate_fees": {
    "limits": [
      {
        "counter": "calculate_fees_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Africa Payments MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON AFRICA PAYMENTS →

Instant setup, no code required.

All 32 Africa Payments MCP tools

FINANCIAL 14 tools
Financial b2c_transfer Send money from business to customer (B2C transfer). Used for payouts, refunds, salaries, and disbursements. Financial bank_transfer Send money directly to a bank account using supported providers. Requires bank account details and bank code. Financial mpesa_b2c Send money from business to customer (B2C). Used for payouts, refunds, salaries. Financial mpesa_stk_push Initiate M-Pesa STK Push (Paybill/Till number payment). Sends payment prompt to customer phone. Financial paystack_initialize Initialize a Paystack transaction. Returns payment link/authorization. Financial paystack_refund Create a refund for a Paystack transaction. Financial paystack_transfer Send money to a bank account or mobile money wallet via Paystack. Financial refund Process a full or partial refund for a completed transaction. The original transaction ID must be provided. Re Financial request_payment Request payment from a customer using STK push (M-Pesa) or payment links. Sends a payment prompt directly to t Financial send_money Send money to a recipient using any available payment provider. Supports mobile money (M-Pesa, MTN MoMo, Airt Financial stk_push Initiate M-Pesa STK Push (SIM Toolkit push) to request payment from a customer. This sends a payment prompt di Financial unified_refund Refund a transaction. Supports full or partial refunds. Financial unified_request_payment Request payment from a customer using the most appropriate provider for their country. Financial unified_send_money Send money to a recipient using the best available provider. Automatically selects the appropriate pr
READ 16 tools
Read calculate_fees Calculate transaction fees for different providers before sending money. Helps compare costs across providers. Read compare_providers Compare payment providers for a specific transaction based on fees, speed, and reliability scores. Helps choos Read get_balance Check the current account balance for a specific payment provider. Balance is returned in the provider Read get_exchange_rates Get current exchange rates between currencies. Supports major African currencies and international currencies. Read get_preferences View your payment preferences including last used provider, recent recipients, and usage statistics. Read get_provider_info Get detailed information about a specific payment provider including supported features, countries, currencies Read get_provider_status Check the health and operational status of all configured providers. Returns uptime status and any known issue Read list_providers List all configured payment providers with their status, supported countries, and currencies. Use this to see Read list_transactions List transactions with optional filtering by date, status, provider, or customer. Results are sorted by date ( Read mpesa_transaction_status Query the status of an M-Pesa transaction. Read paystack_verify Verify a Paystack transaction by reference. Read unified_get_rates Get current exchange rates for African currencies. Read unified_list_transactions List transactions across all providers with filtering options. Read unified_verify_transaction Verify the status of a transaction across any provider. Read validate_phone Validate a phone number format for a specific country and provider. Checks if the phone number is valid for mo Read verify_transaction Check the current status of a transaction across any provider. Use this to confirm if a payment was successful

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Africa Payments MCP

Can an AI agent move money through the Africa Payments MCP server? +

Yes. The Africa Payments MCP server exposes 14 financial tools including b2c_transfer, bank_transfer, mpesa_b2c. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Africa Payments MCP? +

The Africa Payments MCP server has 2 write tools including c2b_register, mpesa_c2b. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Africa Payments MCP.

How many tools does the Africa Payments MCP server expose? +

32 tools across 4 categories: Execute, Financial, Read, Write. 16 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Africa Payments MCP? +

Register the Africa Payments MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Africa Payments MCP tool call.

Deterministic rules across all 32 Africa Payments MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

32 Africa Payments MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.