View all payments made during this session
AI agents call get-payment-history to retrieve information from AI42-MCP X402 Payment 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 payment history data without creating, modifying, deleting, or executing any operations. While the server handles financial transactions through sibling tools (fetch-with-payment, set-payment-limit), this specific tool only reads historical payment data.
From the tool's definition Tool name and description indicate 'View all payments made during this session' - a retrieval operation with no data modification capability. The verb 'View' explicitly denotes read-only access to historical payment records.
Attacks that exploit this kind of access
View all payments made during this session. It is categorised as a Read tool in the AI42-MCP X402 Payment Server MCP Server, which means it retrieves data without modifying state.
Register the AI42-MCP X402 Payment Server MCP server in PolicyLayer and add a rule for get-payment-history: 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 AI42-MCP X402 Payment Server. Nothing to install.
get-payment-history 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 get-payment-history 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 get-payment-history. 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.
get-payment-history is provided by the AI42-MCP X402 Payment Server MCP server (kishore-mk/ai42-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 →