data_lookup

Balances, NFTs, and recent transactions for an address on a public Avalanche chain, via the AvaCloud Data API.

SERVERAvalanche SOURCE@avakit/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-avakit-avalanche/data-lookup.md

WHAT IT DOES

What data_lookup does on Avalanche

AI agents call data_lookup to retrieve information from Avalanche without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why data_lookup is rated Low

Retrieves blockchain data without modifying state or executing code.

From the tool's definition Balances, NFTs, and recent transactions for an address on a public Avalanche chain

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs data_lookup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Avalanche, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_lookup, this is the rule to start with:

data_lookup Allowed

data_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "data_lookup": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Avalanche, apply this rule, and every data_lookup call is checked against it from then on.

FAQ

Questions about data_lookup

What does the data_lookup tool do? +

Balances, NFTs, and recent transactions for an address on a public Avalanche chain, via the AvaCloud Data API. It is categorised as a Read tool in the Avalanche MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on data_lookup? +

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

What risk level is data_lookup? +

data_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit data_lookup? +

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

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

data_lookup is provided by the Avalanche MCP server (@avakit/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Avalanche, and thousands of servers like it.

This server

All 16 Avalanche tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →