Deep analysis of a Hedera token including holder distribution, transfer velocity,
AI agents call token_analyze to retrieve information from Hedera Toolbox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing token data on the Hedera blockchain. It performs no writes, deletions, code execution, or financial transfers. The analysis of holder distribution and transfer velocity are read-only queries of immutable ledger data. While the server charges HBAR micropayments per call, the tool itself performs no financial operations—it merely accesses data.
From the tool's definition Tool name 'token_analyze' and description stating 'Deep analysis of a Hedera token including holder distribution, transfer velocity' indicates querying and analyzing blockchain data without modification or execution of transactions.
Attacks that exploit this kind of access
Deep analysis of a Hedera token including holder distribution, transfer velocity,. It is categorised as a Read tool in the Hedera Toolbox MCP Server, which means it retrieves data without modifying state.
Register the Hedera Toolbox MCP server in PolicyLayer and add a rule for token_analyze: 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 Hedera Toolbox. Nothing to install.
token_analyze is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the token_analyze 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 token_analyze. 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.
token_analyze is provided by the Hedera Toolbox MCP server (mountainmystic/hederatoolbox). 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 →