AI agents call list_payments to retrieve information from Cardzero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays payment history from the wallet's transaction log. It performs no creation, modification, deletion, code execution, or financial transaction. While it operates in a financial context (wallet payments), the tool itself does not move money or commit financial obligations—it merely reads existing transaction records.
From the tool's definition Tool name 'list_payments' and description 'View recent payment history' indicate a query operation that retrieves historical transaction data without modification or side effects.
Attacks that exploit this kind of access
View recent payment history for your CardZero wallet. It is categorised as a Read tool in the Cardzero MCP Server, which means it retrieves data without modifying state.
Register the Cardzero MCP server in PolicyLayer and add a rule for list_payments: 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 Cardzero. Nothing to install.
list_payments 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_payments 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_payments. 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_payments is provided by the Cardzero MCP server (mrocker/cardzero-mcp). 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 →