Burn SPL tokens from the configured wallet. Requires PRIVATE_KEY.
AI agents call burn_tokens to permanently remove resources in Solana MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Burning tokens permanently removes them from existence; this action cannot be undone. Combined with the fact it operates on a real blockchain wallet requiring a PRIVATE_KEY, misuse could result in irreversible loss of valuable token holdings. This clearly falls under Destructive with critical severity given the financial value of tokens and the irreversibility of the action.
From the tool's definition 'Burn SPL tokens' — burning tokens is an irreversible destruction of digital assets from the configured wallet
Attacks that exploit this kind of access
Burn SPL tokens from the configured wallet. Requires PRIVATE_KEY. It is categorised as a Destructive tool in the Solana MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Solana MCP Server MCP server in PolicyLayer and add a rule for burn_tokens: 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 Solana MCP Server. Nothing to install.
burn_tokens 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 burn_tokens 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 burn_tokens. 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.
burn_tokens is provided by the Solana MCP Server MCP server (visioneth/solana-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →