AI agents call paystack_transaction_totals 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 summarizes transaction statistics—a passive data query with no side effects, no financial movement, and no destructive actions. While it exists on a Financial server (Paystack payment processor), the tool itself only reads aggregated transaction information. The severity is low because misuse would only expose transaction summary data, not enable unauthorized payments or deletions.
From the tool's definition Tool name 'paystack_transaction_totals' and description 'Get a summary of transaction statistics' indicate a read-only retrieval operation that queries transaction data without modification or execution of payments.
Attacks that exploit this kind of access
Get a summary of transaction statistics. 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_transaction_totals: 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_transaction_totals 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_transaction_totals 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_transaction_totals. 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_transaction_totals 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 →