List transactions with pagination and filtering options
AI agents call list_transactions to retrieve information from Paystack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries transaction data with no side effects, modifications, or irreversible actions. It supports pagination and filtering for data retrieval only. While it operates on a financial system, the tool itself does not move money, create obligations, or modify state—it merely reads transaction information. Read is the appropriate category.
From the tool's definition Tool name 'list_transactions' and description 'List transactions with pagination and filtering options' indicate data retrieval without modification. The verb 'List' is a classic Read operation that queries existing transaction data.
Documented attack patterns abuse exactly the kind of access list_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Paystack, and nothing reaches the server without passing your rules. This is the rule we recommend for list_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"list_transactions": {}
}
}list_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List transactions with pagination and filtering options. It is categorised as a Read tool in the Paystack MCP Server, which means it retrieves data without modifying state.
Register the Paystack MCP server in PolicyLayer and add a rule for list_transactions: 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 Paystack. Nothing to install.
list_transactions 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 list_transactions 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 list_transactions. 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.
list_transactions is provided by the Paystack MCP server (kohasummons/paystack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Paystack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 Paystack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.