Fetch data for a single asset from Glassnode API. Use this tool when you need to: - Fetch data for ONE specific asset - Get detailed data for a single cryptocurrency IMPORTANT: If you need data for MULTIPLE assets, use fetch_bulk_metrics instead! This tool should only be used for single-asset req...
Risk signalsAccepts URL/endpoint input (endpoint)
Part of the Glassnode server.
Free to start. No card required.
AI agents call fetch_metric 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_metric 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": {
"fetch_metric": {}
}
}See the full Glassnode policy for all 11 tools.
These attack patterns abuse exactly the kind of access fetch_metric 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.
Fetch data for a single asset from Glassnode API. Use this tool when you need to: - Fetch data for ONE specific asset - Get detailed data for a single cryptocurrency IMPORTANT: If you need data for MULTIPLE assets, use fetch_bulk_metrics instead! This tool should only be used for single-asset requests to avoid unnecessary API calls.. It is categorised as a Read tool in the Glassnode MCP Server, which means it retrieves data without modifying state.
Register the Glassnode MCP server in PolicyLayer and add a rule for fetch_metric: 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 Glassnode. Nothing to install.
fetch_metric 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_metric 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 fetch_metric. 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_metric is provided by the Glassnode MCP server (glassnode/glassnode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Glassnode 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.