test_x402_payment
agentscan: Make a real x402 payment to test your wallet and client, with a signed receipt. To check a signed authorization without paying use x402_payment_status; to vet a seller before paying use check_x402_endpoint_before_paying. Returns what the payment gate saw, with an Ed25519-signed UTC rec...
This record as markdown: /tools/dev-tanod-tanod/test-x402-payment.md
What test_x402_payment does on Tanod
AI agents call test_x402_payment to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sha256 | object | — | Optional: a SHA-256 hash as 64 hex characters. It is signed together with the time, as a simple proof that something with this hash existed then. |
Parameters from the server's own tool schema.
Why test_x402_payment is rated Low
Even though test_x402_payment only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs test_x402_payment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_x402_payment, this is the rule to start with:
test_x402_payment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every test_x402_payment call is checked against it from then on.
Questions about test_x402_payment
agentscan: Make a real x402 payment to test your wallet and client, with a signed receipt. To check a signed authorization without paying use x402_payment_status; to vet a seller before paying use check_x402_endpoint_before_paying. Returns what the payment gate saw, with an Ed25519-signed UTC receipt; a sha256 you send is signed with the time, as a simple proof that it existed then. Built for a scheduled health ping: every call settles a new payment on-chain. A failed payment is never settled, and its 402 names the reason (wrong network, amount or payTo, expired or bad signature). The receipt key is at /.well-known/tanod-receipt-key. Typically 1-4 s (one on-chain settlement). Price: USD 0.001. No free tier. Docs: https://tanod.dev/learn/x402-payment-test-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
test_x402_payment accepts 1 parameter: sha256. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for test_x402_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 Tanod. Nothing to install.
test_x402_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 test_x402_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 test_x402_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.
test_x402_payment is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue