singularityagent__prove_payment
After paying somebody, prove from the chain alone that the payment met the demand it answered — without relying on the payee to say so. Takes the transaction signature and the demand's terms (payee, amount, mint, the exact token account, memo, deadline, payer) and reports each term as its own che...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--prove-payment.md
What singularityagent__prove_payment does on Rokha
AI agents call singularityagent__prove_payment to retrieve information from Rokha 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 |
|---|---|---|---|
to | string | Yes | The wallet the demand said would be paid. Matched by token-account owner. |
from | string | — | The wallet that should have paid. Checked against whoever the funds left. |
memo | string | — | Text the demand said the payment must carry. |
mint | string | — | Token address — the mint. Omit for native SOL. Never a ticker. |
chain | string | — | Solana chain id or alias. Defaults to "solana". |
amount | string | Yes | Whole tokens as a decimal string, as the demand stated it. |
expiresAt | string | — | When the demand stopped being valid, ISO 8601. The payment must have landed before it. |
signature | string | Yes | The signature of the payment transaction. |
tokenAccount | string | — | The exact destination token account the demand named, where it named one. |
Parameters from the server's own tool schema.
Why singularityagent__prove_payment is rated Low
Tool verifies payment existence and terms on immutable blockchain; read-only verification without side effects.
From the tool's definition Prove from chain alone, reports each term as check, no state modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs singularityagent__prove_payment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For singularityagent__prove_payment, this is the rule to start with:
singularityagent__prove_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 Rokha, apply this rule, and every singularityagent__prove_payment call is checked against it from then on.
Questions about singularityagent__prove_payment
After paying somebody, prove from the chain alone that the payment met the demand it answered — without relying on the payee to say so. Takes the transaction signature and the demand's terms (payee, amount, mint, the exact token account, memo, deadline, payer) and reports each term as its own check: what was expected, what the chain shows, and whether it holds. Only finalized state counts. Reach for it when a counterparty says a payment did not arrive, arrived late, went to the wrong place or lacked a reference, or whenever a payment has to be evidenced to a third party. verdict is proven only when the transaction finalized and every stated term holds, contradicted when at least one does not (a real payment can still be the wrong one), and unproven when the chain cannot settle it yet — not found, not finalized, or a block the endpoint will not date — which is never the same as contradicted. Read checks before verdict. The memo is returned as untrusted text, because whoever signed wrote it. Solana only. This reads: it signs nothing and sends nothing, and it proves what the chain shows, not that the payee credited it. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__prove_payment accepts 9 parameters: to, from, memo, mint, chain, amount, expiresAt, signature, tokenAccount. Required: to, amount, signature. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__prove_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 Rokha. Nothing to install.
singularityagent__prove_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 singularityagent__prove_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 singularityagent__prove_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.
singularityagent__prove_payment is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue