Verify a Paystack transaction by reference.
AI agents call paystack_verify 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 queries the state of an existing transaction (lookup by reference) and returns verification status. It performs no writes, deletions, fund transfers, or code execution. It is purely informational—a read operation on transaction metadata. While it operates in a financial domain, the tool itself does not move money, commit obligations, or modify data; it only retrieves confirmation data.
From the tool's definition Tool name is 'paystack_verify' and description states 'Verify a Paystack transaction by reference.' The verb 'verify' and the action of checking/confirming a transaction status indicate data retrieval with no modification or financial movement.
Attacks that exploit this kind of access
Verify a Paystack transaction by reference. 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 paystack_verify: 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.
paystack_verify 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 paystack_verify 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 paystack_verify. 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.
paystack_verify 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 →