AI agents call get-total-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 only reads and aggregates existing transaction data from Paystack. It has no side effects, performs no state changes, and poses minimal risk even if misused by an AI agent—the worst outcome is exposure of transaction metadata already visible to an authenticated user.
From the tool's definition Tool description states it 'Get[s] categorized totals of Paystack transactions by status' - retrieves and queries transaction data without modifying or deleting anything.
Attacks that exploit this kind of access
Get categorized totals of Paystack transactions by status. 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 get-total-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.
get-total-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 get-total-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 get-total-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.
get-total-transactions is provided by the Paystack MCP server (johnnieemmanuel/paystack-mcp-server). 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 →