singularityagent__verify_burn
Confirm that a Solana transaction really burned a token: which mint, which owner, how much, at finalized commitment. Pass mint (and optionally owner and a minimum amount) to check the burn against a claim rather than just describing it — a transaction that burned a different mint is refused by na...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--verify-burn.md
What singularityagent__verify_burn does on Rokha
AI agents call singularityagent__verify_burn 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 |
|---|---|---|---|
mint | string | — | The mint the burn must be of. Matched by address, never by symbol. |
chain | string | — | Solana chain id or alias. Defaults to "solana". |
owner | string | — | The wallet that must have signed the burn. |
minimum | string | — | The least that must have been destroyed, as a human decimal amount, e.g. "1000". |
signature | string | Yes | The transaction signature of the burn. |
expectMemo | string | — | Text the burn's memo must contain. The memo is the only part of the transaction the burner wrote and signed, so it is what makes a burn attributable to a claima |
Parameters from the server's own tool schema.
Why singularityagent__verify_burn is rated Low
Verifies and reads blockchain transaction state without modifying or executing financial operations.
From the tool's definition Confirm that a Solana transaction burned a token; reports whether signature redeemed; never spends.
Attacks that exploit this kind of access
The rule that runs singularityagent__verify_burn 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__verify_burn, this is the rule to start with:
singularityagent__verify_burn 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__verify_burn call is checked against it from then on.
Questions about singularityagent__verify_burn
Confirm that a Solana transaction really burned a token: which mint, which owner, how much, at finalized commitment. Pass mint (and optionally owner and a minimum amount) to check the burn against a claim rather than just describing it — a transaction that burned a different mint is refused by name. Reports whether the signature has already been redeemed, and never spends it. A signature is public the moment it lands, so this proves a burn happened and proves nothing about who quoted it; what binds a burn to a claimant is the memo the burner signed into it, which is returned when there is one. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__verify_burn accepts 6 parameters: mint, chain, owner, minimum, signature, expectMemo. Required: 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__verify_burn: 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__verify_burn 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__verify_burn 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__verify_burn. 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__verify_burn 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