Request payment from a customer using STK push (M-Pesa) or payment links. Sends a payment prompt directly to the customer
AI agents use request_payment to commit financial operations through Africa Payments MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a financial transaction by sending a payment request directly to a customer's device or via a payment link. It triggers real monetary movement obligations and directly involves payment processing infrastructure (M-Pesa STK push), making it clearly Financial in category.
From the tool's definition 'Request payment from a customer using STK push (M-Pesa) or payment links. Sends a payment prompt directly to the customer'
Attacks that exploit this kind of access
Request payment from a customer using STK push (M-Pesa) or payment links. Sends a payment prompt directly to the customer. It is categorised as a Financial tool in the Africa Payments MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Africa Payments MCP server in PolicyLayer and add a rule for request_payment: 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 Africa Payments MCP. Nothing to install.
request_payment 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 request_payment 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 request_payment. 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.
request_payment is provided by the Africa Payments MCP server (kenyaclaw/africa-payments-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →