Convert a metric path to a metric code for use in Glassnode Studio. This tool helps convert metric paths (e.g., 'market/price_usd_close') to metric codes (e.g., 'market.PriceUsdClose') that can be used in Studio link generation. Use this tool when: - Users ask for Studio links - You need to pro...
Part of the Glassnode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call path_to_metric_code 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 path_to_metric_code 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:
path_to_metric_code:
rules:
- action: allowSee the full Glassnode policy for all 11 tools.
Agents calling read-class tools like path_to_metric_code 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.
Convert a metric path to a metric code for use in Glassnode Studio. This tool helps convert metric paths (e.g., 'market/price_usd_close') to metric codes (e.g., 'market.PriceUsdClose') that can be used in Studio link generation. Use this tool when: - Users ask for Studio links - You need to provide metric codes for external tools - Converting API paths to Studio-compatible identifiers. 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 path_to_metric_code. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Glassnode MCP server.
path_to_metric_code 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 path_to_metric_code 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 path_to_metric_code. 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.
path_to_metric_code 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