token_associate · HashPilot MCP: Risk & Policy

WHAT IT DOES

What token_associate does on HashPilot

AI agents use token_associate to create or update resources in HashPilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HashPilot environment.

WHY IT NEEDS A POLICY

Why token_associate needs a policy

Token association modifies the account's state on the Hedera blockchain by linking a token to it, enabling future token transfers. This is a reversible on-chain write operation (tokens can be disassociated), not destructive, financial, or code execution. However, it does require a private key signature, meaning misuse could associate unwanted tokens with an account.

From the tool's definition Associate a token with an account to enable receiving/holding tokens. Required before an account can receive tokens.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

token_associate Rate-limited

token_associate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_associate": {
      "limits": [
        {
          "counter": "token_associate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_associate

What does the token_associate tool do? +

Associate a token with an account to enable receiving/holding tokens. Required before an account can receive tokens. The account must sign the transaction - provide privateKey or ensure account is in address book with private key. It is categorised as a Write tool in the HashPilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on token_associate? +

Register the HashPilot MCP server in PolicyLayer and add a rule for token_associate: 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_associate? +

token_associate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit token_associate? +

Yes. Add a rate_limit block to the token_associate 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_associate completely? +

Set action: deny in the PolicyLayer policy for token_associate. 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_associate? +

token_associate 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.