Burn tokens from the treasury account, reducing total supply. Requires supply key to be enabled on the token. Operator must have the supply key.
AI agents call token_burn to permanently remove resources in HashPilot — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Burning tokens is an irreversible blockchain operation that permanently destroys tokens and reduces total supply. It cannot be undone once executed on the Hedera ledger. This qualifies as Destructive. The blast radius is high because an AI agent misusing this tool could permanently destroy significant token holdings from the treasury account.
From the tool's definition 'Burn tokens from the treasury account, reducing total supply' — burning tokens is irreversible and permanently reduces the token supply
Attacks that exploit this kind of access
Burn tokens from the treasury account, reducing total supply. Requires supply key to be enabled on the token. Operator must have the supply key. It is categorised as a Destructive tool in the HashPilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HashPilot MCP server in PolicyLayer and add a rule for token_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 HashPilot. Nothing to install.
token_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 token_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 token_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.
token_burn is provided by the HashPilot MCP server (justmert/hashpilot). 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 →