get_etf_history_eth

What get_etf_history_eth does on REI Crypto MCP Server

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

Why get_etf_history_eth is rated Low

This tool retrieves historical ETF data related to Ethereum. It performs a GET request, which is inherently a read operation with no side effects. The context of a crypto data aggregator server and the presence of similar read-only tools (get_active_users, get_batch_historical_prices, get_bridge_volume) confirm this is a data query tool. There is no capacity to execute code, delete data, or move funds.

From the tool's definition Tool name 'get_etf_history_eth' and description 'GET /etfs/historyEth' indicate a read-only data retrieval operation. No modification, deletion, code execution, or financial transaction capability is implied.

The rule that runs get_etf_history_eth safely

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

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

Questions about get_etf_history_eth