Verify if a x402 payment was received and settled on-chain
AI agents call verify_payment to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and checks the status of a payment—a read-only operation with no side effects or state changes. While it involves financial data (payment verification), it does not move money, commit financial obligations, or execute transactions; it merely queries existing payment settlement status.
From the tool's definition Tool name 'verify_payment' and description 'Verify if a x402 payment was received and settled on-chain' indicate a query operation that retrieves payment status information without modifying or executing transactions.
Documented attack patterns abuse exactly the kind of access verify_payment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_payment:
{
"version": "1",
"default": "deny",
"tools": {
"verify_payment": {}
}
} verify_payment is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify if a x402 payment was received and settled on-chain. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for verify_payment: 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 Mcp Afip. Nothing to install.
verify_payment 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 verify_payment 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 verify_payment. 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.
verify_payment is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.