burn_and_close

Burn worthless dust tokens and close the accounts in one step, reclaiming rent SOL. For accounts with small leftover token balances that cannot be closed directly. Uses dry-run/confirm pattern.

Server RefundYourSOL refundyoursol/refundyoursol-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What burn_and_close does on RefundYourSOL

AI agents call burn_and_close to permanently remove resources in RefundYourSOL — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why burn_and_close needs a policy

Burning tokens permanently destroys them from existence on-chain with no recovery path. Closing token accounts is also irreversible. Even though the tokens are described as 'worthless dust,' an AI agent misusing this tool could burn tokens with real value or close accounts the user still needs.

From the tool's definition 'Burn worthless dust tokens and close the accounts in one step' — burning tokens is irreversible destruction of on-chain assets; closing accounts reclaims rent SOL permanently. Both actions cannot be undone.

Questions about burn_and_close

What does the burn_and_close tool do? +

Burn worthless dust tokens and close the accounts in one step, reclaiming rent SOL. For accounts with small leftover token balances that cannot be closed directly. Uses dry-run/confirm pattern. It is categorised as a Destructive tool in the RefundYourSOL MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on burn_and_close? +

Register the RefundYourSOL MCP server in PolicyLayer and add a rule for burn_and_close: 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 RefundYourSOL. Nothing to install.

What risk level is burn_and_close? +

burn_and_close is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit burn_and_close? +

Yes. Add a rate_limit block to the burn_and_close 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.

How do I block burn_and_close completely? +

Set action: deny in the PolicyLayer policy for burn_and_close. 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.

What MCP server provides burn_and_close? +

burn_and_close is provided by the RefundYourSOL MCP server (refundyoursol/refundyoursol-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.