singularityagent__receipt_art
Every Singularity payment QR is artwork derived from the payment's reference — the pubkey attached to the transfer that makes it findable on chain. Because it is derived rather than stored, the picture is a fingerprint of one payment: two payments can never render alike, and anyone holding the re...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--receipt-art.md
What singularityagent__receipt_art does on Rokha
AI agents call singularityagent__receipt_art 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 |
|---|---|---|---|
uri | string | — | A receipt metadata uri to read the reference out of, when you do not have it directly. |
link | string | — | The solana: payment link, needed to render or compare a picture. |
image | string | — | An SVG to check against what the reference generates. Requires `link`. |
reference | string | — | The payment reference the art is derived from. |
Parameters from the server's own tool schema.
Why singularityagent__receipt_art is rated Low
Retrieves and displays payment metadata as visual art; no modification, execution, or financial transaction capability.
From the tool's definition derives artwork from payment reference, retrieves style traits, renders QR code
Risk signalsAccepts URL/endpoint input (uri) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs singularityagent__receipt_art 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__receipt_art, this is the rule to start with:
singularityagent__receipt_art 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__receipt_art call is checked against it from then on.
Questions about singularityagent__receipt_art
Every Singularity payment QR is artwork derived from the payment's reference — the pubkey attached to the transfer that makes it findable on chain. Because it is derived rather than stored, the picture is a fingerprint of one payment: two payments can never render alike, and anyone holding the reference can re-derive it. Pass a reference (or a receipt uri of the form <base>/<reference>.json, which is how the reference reaches the chain) to get the style traits a marketplace would list. Pass link as well to render the code. Pass image to ask the question that matters: is this picture the one this reference generates? A receipt NFT's metadata is served by a host that can change it, and this is how a holder checks the image they are being shown is evidence of their payment rather than something swapped in. matches: false is not proof of fraud — it means the image is not evidence. This is pure: it reads no chain, fetches nothing, and signs nothing. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__receipt_art accepts 4 parameters: uri, link, image, reference. 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__receipt_art: 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__receipt_art 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__receipt_art 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__receipt_art. 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__receipt_art 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