AI agents call paystack_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.
Despite operating within a financial payment system, 'list_transactions' retrieves and queries transaction data without modifying state, committing funds, or executing irreversible actions. It is a Read operation. Severity is medium rather than low because transaction data is sensitive financial information whose exposure could inform fraud or other attacks, even though the tool itself causes no direct harm.
From the tool's definition Tool name 'paystack_list_transactions' indicates a retrieval/query operation. The sibling tools include financial operations (paystack_initialize_transaction, paystack_verify_transaction, paystack_create_payment_page), but this specific tool's name pattern…
Attacks that exploit this kind of access
paystack_list_transactions. 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 paystack_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.
paystack_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 paystack_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 paystack_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.
paystack_list_transactions is provided by the Paystack MCP server (trinity-21/mcp-server-paystack). 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 →