export_transactions

THE RISK

Low Risk

Why export_transactions needs a policy

This tool retrieves/exports transaction data without modifying or deleting anything. It is a read operation. Severity is medium because transaction data is sensitive financial information that could be misused if exposed to unauthorized parties.

From the tool's definition Export a list of transactions carried out on your integration

Documented attack patterns abuse exactly the kind of access export_transactions gives an agent:

POLICY

How to control export_transactions

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 export_transactions:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_transactions": {}
  }
}

export_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Paystack — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Paystack tools

Financial initialize_transaction Initialize a transaction to accept payment on Paystack Financial charge_authorization Charge a previously authorized card Financial finalize_disable_otp Finalize the request to disable OTP on your transfers Financial partial_debit Charge a partial amount from a previously authorized card Financial disable_transfers_otp Disable OTP requirement for transfers Financial enable_transfers_otp Enable OTP requirement for transfers Destructive deactivate_authorization Deactivate a payment authorization when a card needs to be forgotten Execute resend_transfers_otp Generates a new OTP and sends to customer for transfer verification

All 28 Paystack tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about export_transactions

What does the export_transactions tool do? +

Export a list of transactions carried out on your integration. It is categorised as a Read tool in the Paystack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_transactions? +

Register the Paystack MCP server in PolicyLayer and add a rule for export_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.

What risk level is export_transactions? +

export_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_transactions? +

Yes. Add a rate_limit block to the export_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.

How do I block export_transactions completely? +

Set action: deny in the PolicyLayer policy for export_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.

What MCP server provides export_transactions? +

export_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.

Enforce policy on every Paystack tool call.

Start from Paystack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →