freeze_address
Freeze an address for a specific token, preventing all transfers.
This record as markdown: /tools/network-tenzro-tenzro/freeze-address.md
What freeze_address does on Tenzro Ledger MCP
AI agents call freeze_address 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.
Why freeze_address is rated Critical
Freezing an address prevents all token transfers from/to that address, which is a severe and potentially irreversible action that can lock funds and disrupt financial operations. This goes beyond a simple write operation as it blocks financial activity and may not be easily reversible depending on the protocol.
From the tool's definition Freeze an address for a specific token, preventing all transfers
Attacks that exploit this kind of access
The rule that runs freeze_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For freeze_address, this is the rule to start with:
freeze_address 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 Tenzro Ledger MCP, apply this rule, and every freeze_address call is checked against it from then on.
Questions about freeze_address
Freeze an address for a specific token, preventing all transfers. 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 freeze_address: 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.
freeze_address 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 freeze_address 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 freeze_address. 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.
freeze_address 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.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue