Query the status of an M-Pesa transaction.
AI agents call mpesa_transaction_status to retrieve information from Africa Payments MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction status information without side effects. It is a read-only operation that queries existing data. While it exists in a financial payments context, the tool itself does not move money, commit financial obligations, or modify state—it only provides visibility into transaction history. Severity is low because querying transaction status poses minimal risk of harmful AI agent misuse.
From the tool's definition Tool name and description indicate a query operation: 'Query the status of an M-Pesa transaction.' No modification, execution, deletion, or financial movement is performed.
Attacks that exploit this kind of access
Query the status of an M-Pesa transaction. It is categorised as a Read tool in the Africa Payments MCP MCP Server, which means it retrieves data without modifying state.
Register the Africa Payments MCP server in PolicyLayer and add a rule for mpesa_transaction_status: 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.
mpesa_transaction_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mpesa_transaction_status 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 mpesa_transaction_status. 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.
mpesa_transaction_status 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 →