get_etf_history

GET /etfs/history

SERVERREI Crypto MCP Server SOURCE0xreisearch/crypto-mcp-beta

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-etf-history.md

WHAT IT DOES

What get_etf_history does on REI Crypto MCP Server

AI agents call get_etf_history 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.

RISK

Why get_etf_history is rated Low

This tool queries historical ETF data without side effects, authorization changes, financial transactions, or code execution. It is a read-only data retrieval operation consistent with the server's purpose of providing crypto market data. No destructive, financial, or executable operations are evident.

From the tool's definition Tool name 'get_etf_history' and description 'GET /etfs/history' indicate a retrieval operation with no write, delete, or execute capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_etf_history 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, this is the rule to start with:

get_etf_history Allowed

get_etf_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect REI Crypto MCP Server, apply this rule, and every get_etf_history call is checked against it from then on.

FAQ

Questions about get_etf_history

What does the get_etf_history tool do? +

GET /etfs/history. It is categorised as a Read tool in the REI Crypto MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_etf_history? +

Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_etf_history: 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.

What risk level is get_etf_history? +

get_etf_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_etf_history? +

Yes. Add a rate_limit block to the get_etf_history 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.

How do I block get_etf_history completely? +

Set action: deny in the PolicyLayer policy for get_etf_history. 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.

What MCP server provides get_etf_history? +

get_etf_history 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.

KEEP EXPLORING

More on REI Crypto MCP Server, and thousands of servers like it.

This server

All 117 REI Crypto MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →