list_transactions

List recent transactions across your cards.

SERVERAgentpay SOURCEagentpay-mcp-server

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentpay/list-transactions.md

WHAT IT DOES

What list_transactions does on Agentpay

AI agents call list_transactions to retrieve information from Agentpay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`limit`	integer	—	Max results
`card_id`	string	—	Filter by card

Parameters from the server's own tool schema.

RISK

Why list_transactions is rated Low

This tool queries transaction history and retrieves financial data without modifying, deleting, or executing transactions. Although it exposes sensitive financial information (transaction records) in the context of a payment platform, the action itself is read-only.

From the tool's definition Tool description states 'List recent transactions across your cards' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_transactions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_transactions, this is the rule to start with:

list_transactions Allowed

list_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every list_transactions call is checked against it from then on.

FAQ

Questions about list_transactions

What does the list_transactions tool do? +

List recent transactions across your cards. It is categorised as a Read tool in the Agentpay MCP Server, which means it retrieves data without modifying state.

What parameters does list_transactions accept? +

list_transactions accepts 2 parameters: limit, card_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_transactions? +

Register the Agentpay MCP server in PolicyLayer and add a rule for 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 Agentpay. Nothing to install.

What risk level is list_transactions? +

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

Can I rate-limit list_transactions? +

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

How do I block list_transactions completely? +

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

What MCP server provides list_transactions? +

list_transactions is provided by the Agentpay MCP server (agentpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agentpay, and thousands of servers like it.

This server

All 17 Agentpay tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →