Prepares a transaction to burn tokens
AI agents call prepare-burn-token-factory-tokens to permanently remove resources in Osmosis MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Burning tokens permanently destroys them from circulation on the Osmosis blockchain. This is an irreversible action - once tokens are burned, they cannot be recovered. The 'prepare' prefix suggests it stages the transaction rather than executing it immediately, but the intent and effect of the transaction itself is destructive.
From the tool's definition 'burn tokens' - burning tokens is an irreversible destruction of digital assets that cannot be undone
Attacks that exploit this kind of access
Prepares a transaction to burn tokens. It is categorised as a Destructive tool in the Osmosis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for prepare-burn-token-factory-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 Osmosis MCP Server. Nothing to install.
prepare-burn-token-factory-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 prepare-burn-token-factory-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 prepare-burn-token-factory-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.
prepare-burn-token-factory-tokens is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →