three_burn
Burn a USD-denominated amount of the $THREE your wallet holds. Quotes USD→$THREE via Jupiter, then sends ONE Solana transaction that splits it between the incinerator (burn) and the three.ws treasury, per the live public token config. EXECUTION ACTION — signs and broadcasts on Solana mainnet, IRR...
This record as markdown: /tools/io-github-nirholas-three-token-mcp/three-burn.md
What three_burn does on $THREE Token
AI agents call three_burn to permanently remove resources in $THREE Token, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
usd | number | Yes | USD value of $THREE to burn (priced live via Jupiter). |
memo | string | — | Optional note appended to the on-chain memo. |
secret | string | — | Base58 signer override. Defaults to SOLANA_SECRET_KEY. Treat like cash. |
burnBps | number | — | Share routed to the incinerator in basis points. Default 5000 (50% burn / 50% treasury). 10000 = burn everything. |
confirm | boolean | — | Must be true to execute this irreversible burn (when REQUIRE_CONFIRM is on). |
Parameters from the server's own tool schema.
Why three_burn is rated Critical
This tool irreversibly destroys (burns) cryptocurrency tokens, which cannot be undone. While it also involves financial value (moving cryptocurrency), the primary and defining characteristic is permanent destruction of assets. Destructive takes precedence over Financial in severity ranking.
From the tool's definition Tool description explicitly states: 'Burn a USD-denominated amount of the $THREE your wallet holds', 'IRREVERSIBLE: pass confirm:true', and 'signs and broadcasts on Solana mainnet'.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs three_burn safely
PolicyLayer is an MCP gateway: it sits between your AI agents and $THREE Token, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For three_burn, this is the rule to start with:
three_burn is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect $THREE Token, apply this rule, and every three_burn call is checked against it from then on.
Questions about three_burn
Burn a USD-denominated amount of the $THREE your wallet holds. Quotes USD→$THREE via Jupiter, then sends ONE Solana transaction that splits it between the incinerator (burn) and the three.ws treasury, per the live public token config. EXECUTION ACTION — signs and broadcasts on Solana mainnet, IRREVERSIBLE: pass confirm:true. Capped by MAX_BURN_USD. The resolved mint is asserted to be canonical $THREE before signing. Requires a signer (SOLANA_SECRET_KEY env or the secret arg) holding enough $THREE. Returns the tx signature, the burned/treasury breakdown, and a Solscan link. It is categorised as a Destructive tool in the $THREE Token MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
three_burn accepts 5 parameters: usd, memo, secret, burnBps, confirm. Required: usd. The full parameter table on this page comes from the server's own tool schema.
Register the $THREE Token MCP server in PolicyLayer and add a rule for three_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 $THREE Token. Nothing to install.
three_burn is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the three_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 three_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.
three_burn is provided by the $THREE Token MCP server (@three-ws/three-token-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on $THREE Token, and thousands of servers like it.
Across the catalogue