burn_blocked_tokens
Burn tokens held by a blocked address (compliance seizure).
This record as markdown: /tools/arome3-tempo-mcp/burn-blocked-tokens.md
What burn_blocked_tokens does on Tempo
AI agents call burn_blocked_tokens to permanently remove resources in Tempo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why burn_blocked_tokens is rated Critical
Burning tokens permanently destroys them with no possibility of recovery. Combined with the financial nature of the stablecoin context and the fact that this operates on a blocked address's holdings, misuse could result in irreversible loss of real monetary value.
From the tool's definition 'Burn tokens held by a blocked address (compliance seizure)' — burning tokens is an irreversible destruction of financial assets
Attacks that exploit this kind of access
The rule that runs burn_blocked_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For burn_blocked_tokens, this is the rule to start with:
burn_blocked_tokens 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 Tempo, apply this rule, and every burn_blocked_tokens call is checked against it from then on.
Questions about burn_blocked_tokens
Burn tokens held by a blocked address (compliance seizure). It is categorised as a Destructive tool in the Tempo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tempo MCP server in PolicyLayer and add a rule for burn_blocked_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 Tempo. Nothing to install.
burn_blocked_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_blocked_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_blocked_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_blocked_tokens is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tempo, and thousands of servers like it.
Across the catalogue