Open frozen token to public trading. Irreversible.
AI agents call unfreeze_token to permanently remove resources in Basis MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently modifies token state by making a frozen token tradeable to the public. This is an irreversible operation with potentially severe financial consequences—once unfrozen, the token enters public circulation and the action cannot be reversed. The blast radius is critical: unauthorized use could expose a token project to unintended liquidity, manipulation, or loss of control over token distribution.
From the tool's definition Tool description explicitly states "Open frozen token to public trading. Irreversible." The irreversible nature of unfreezing a token that was previously frozen indicates a state change that cannot be undone.
Attacks that exploit this kind of access
Open frozen token to public trading. Irreversible. It is categorised as a Destructive tool in the Basis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for unfreeze_token: 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 Basis MCP Server. Nothing to install.
unfreeze_token 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 unfreeze_token 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 unfreeze_token. 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.
unfreeze_token is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →