List all transactions with optional filters. Returns paginated transaction data including pagination metadata (first, last, previous, next page links). SMART FILTER: If you have a payer_email from a previous payment creation (stored from create_payment_intent response), ask user:
AI agents call list_transactions to retrieve information from Bayarcash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries transaction history with optional filters. While it accesses financial transaction data (which elevates severity above 'low'), it performs no write, execute, destructive, or financial operations.
From the tool's definition Tool description states 'List all transactions' and 'Returns paginated transaction data', indicating data retrieval without modification. No language about creation, deletion, or financial commitment.
Attacks that exploit this kind of access
List all transactions with optional filters. Returns paginated transaction data including pagination metadata (first, last, previous, next page links). SMART FILTER: If you have a payer_email from a previous payment creation (stored from create_payment_intent response), ask user:. It is categorised as a Read tool in the Bayarcash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bayarcash MCP Server 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 Bayarcash MCP Server. Nothing to install.
list_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 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.
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.
list_transactions is provided by the Bayarcash MCP Server MCP server (webimpianteam/bayarcash-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 →