Fetch data for multiple assets efficiently using Glassnode's bulk endpoint. PREFERRED: Use this tool when you need to: - Fetch the same metric for MULTIPLE assets (2 or more) - Compare data across different cryptocurrencies - Get comprehensive market data for several assets - Avoid making multip...
Accepts URL/endpoint input (endpoint); Single-target operation
Part of the Glassnode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call fetch_bulk_metrics to retrieve information from Glassnode 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 fetch_bulk_metrics 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.
tools:
fetch_bulk_metrics:
rules:
- action: allowSee the full Glassnode policy for all 11 tools.
Agents calling read-class tools like fetch_bulk_metrics have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Fetch data for multiple assets efficiently using Glassnode's bulk endpoint. PREFERRED: Use this tool when you need to: - Fetch the same metric for MULTIPLE assets (2 or more) - Compare data across different cryptocurrencies - Get comprehensive market data for several assets - Avoid making multiple individual API calls EFFICIENCY TIP: Always batch multiple asset requests into a single call instead of making separate fetch_metric calls for each asset.. It is categorised as a Read tool in the Glassnode MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for fetch_bulk_metrics. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Glassnode MCP server.
fetch_bulk_metrics 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 fetch_bulk_metrics rule in your Intercept 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 Intercept policy for fetch_bulk_metrics. 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.
fetch_bulk_metrics is provided by the Glassnode MCP server (glassnode/glassnode-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept