Get total amount received on your account
AI agents call 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 data from a financial account. It performs a read-only query to display totals—no money is moved, no data is modified, and no irreversible actions occur. While it accesses financial information, the actual capability is purely informational lookup, which is characteristic of Read category tools.
From the tool's definition Tool name 'transaction_totals' and description 'Get total amount received on your account' indicate a query operation that retrieves aggregated financial data without modification or movement of funds.
Documented attack patterns abuse exactly the kind of access transaction_totals 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 transaction_totals:
{
"version": "1",
"default": "deny",
"tools": {
"transaction_totals": {}
}
}transaction_totals 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.
Get total amount received on your account. 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 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.
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 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 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.
transaction_totals 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.