Query HD wallet data for EVM blockchains by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use
Part of the Mcp Hd Wallet server.
Free to start. No card required.
AI agents call hd_wallet_data_evm to retrieve information from Mcp Hd Wallet without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though hd_wallet_data_evm only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"hd_wallet_data_evm": {}
}
}See the full Mcp Hd Wallet policy for all 4 tools.
These attack patterns abuse exactly the kind of access hd_wallet_data_evm gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Query HD wallet data for EVM blockchains by extended public key (xPub). The wallet must first be synced via manage_hd_wallet. Offset pagination: use. It is categorised as a Read tool in the Mcp Hd Wallet MCP Server, which means it retrieves data without modifying state.
Register the Mcp Hd Wallet MCP server in PolicyLayer and add a rule for hd_wallet_data_evm: 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 Mcp Hd Wallet. Nothing to install.
hd_wallet_data_evm 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 hd_wallet_data_evm 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 hd_wallet_data_evm. 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.
hd_wallet_data_evm is provided by the Mcp Hd Wallet MCP server (@cryptoapis-io/mcp-hd-wallet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Mcp Hd Wallet tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.