AI agents call list_transactions to retrieve information from ClawPay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical transaction data. It has no side effects—it does not create, modify, delete, or execute payments. While the server context involves financial operations, this specific tool is limited to querying past transactions, which is a Read action. Severity is low because retrieving transaction history alone does not create financial risk or commit financial obligations.
From the tool's definition Tool name 'list_transactions' and description 'List recent payment transactions' indicate a read-only query operation that retrieves transaction history without modifying, deleting, or executing payment actions.
Attacks that exploit this kind of access
List recent payment transactions. It is categorised as a Read tool in the ClawPay MCP Server, which means it retrieves data without modifying state.
Register the ClawPay 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 ClawPay. 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 ClawPay MCP server (xodn348/clawpay). 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 →