GET /etfs/historyEth
AI agents call get_etf_history_eth to retrieve information from REI Crypto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
GET /etfs/historyEth. It is categorised as a Read tool in the REI Crypto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_etf_history_eth: 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 REI Crypto MCP Server. Nothing to install.
get_etf_history_eth 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 get_etf_history_eth 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 get_etf_history_eth. 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.
get_etf_history_eth is provided by the REI Crypto MCP Server MCP server (0xreisearch/crypto-mcp-beta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_etf_history_eth is one line of REI Crypto MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →