Record a redemption (decrement circulating).
AI agents call secure_mint_record_burn to permanently remove resources in Tenzro Ledger MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Burning or redeeming tokens is an irreversible financial/destructive operation that permanently removes tokens from circulation. It cannot be undone. While it also has financial implications, the irreversible destruction of token supply places it in the Destructive category (which outranks Write but is peer to Financial).
From the tool's definition 'Record a redemption (decrement circulating)' — burning/redeeming tokens irreversibly decrements circulating supply
Attacks that exploit this kind of access
Record a redemption (decrement circulating). It is categorised as a Destructive tool in the Tenzro Ledger MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for secure_mint_record_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 Tenzro Ledger MCP. Nothing to install.
secure_mint_record_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 secure_mint_record_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 secure_mint_record_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.
secure_mint_record_burn is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/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 →