token_freeze · HashPilot MCP: Risk & Policy

WHAT IT DOES

What token_freeze does on HashPilot

AI agents invoke token_freeze to trigger actions in HashPilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why token_freeze needs a policy

This tool triggers an external blockchain operation that changes the state of a token account on the Hedera network by freezing it, preventing any transfers. It is not purely destructive (data is not deleted) but it executes a consequential on-chain transaction with significant real-world impact — blocking all token transfers for the targeted account.

From the tool's definition Freeze a token for a specific account, preventing transfers. Requires freeze key to be enabled on the token.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

token_freeze Rate-limited

token_freeze stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "token_freeze": {
      "limits": [
        {
          "counter": "token_freeze_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HashPilot, so you can run agents against it safely.

FAQ

Questions about token_freeze

What does the token_freeze tool do? +

Freeze a token for a specific account, preventing transfers. Requires freeze key to be enabled on the token. Operator must have the freeze key. It is categorised as a Execute tool in the HashPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on token_freeze? +

Register the HashPilot MCP server in PolicyLayer and add a rule for token_freeze: 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 HashPilot. Nothing to install.

What risk level is token_freeze? +

token_freeze is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit token_freeze? +

Yes. Add a rate_limit block to the token_freeze 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.

How do I block token_freeze completely? +

Set action: deny in the PolicyLayer policy for token_freeze. 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.

What MCP server provides token_freeze? +

token_freeze is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.