verify_transaction

Check the current status of a transaction across any provider. Use this to confirm if a payment was successful, pending, or failed. Works with transaction IDs from any provider.

Server Africa Payments MCP kenyaclaw/africa-payments-mcp
Category Read
Risk class Low
Parameters 00 required

What verify_transaction does on Africa Payments MCP

AI agents call verify_transaction 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.

Why verify_transaction needs a policy

verify_transaction is a read-only operation that retrieves transaction status information. It does not process payments, transfer funds, delete records, or execute any code. While the server handles sensitive financial data, this specific tool only queries status without initiating or altering transactions.

From the tool's definition Tool description states it "Check[s] the current status of a transaction" and "confirm[s] if a payment was successful, pending, or failed." These are query/retrieval operations with no modification or execution of side effects.

Questions about verify_transaction

What does the verify_transaction tool do? +

Check the current status of a transaction across any provider. Use this to confirm if a payment was successful, pending, or failed. Works with transaction IDs from any provider. It is categorised as a Read tool in the Africa Payments MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_transaction? +

Register the Africa Payments MCP server in PolicyLayer and add a rule for verify_transaction: 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.

What risk level is verify_transaction? +

verify_transaction is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_transaction? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.