get_networks_history
GET /networks/history/{chain}
This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-networks-history.md
What get_networks_history does on REI Crypto MCP Server
AI agents call get_networks_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.
Why get_networks_history is rated Low
This tool retrieves historical data about blockchain networks. It uses the HTTP GET method, which is inherently read-only with no side effects. The endpoint structure '{chain}' parameter suggests querying historical statistics for a specific blockchain network. No data creation, modification, deletion, code execution, or financial transactions are possible with a GET request.
From the tool's definition Tool name 'get_networks_history' with GET endpoint and description 'GET /networks/history/{chain}' indicates a data retrieval operation. The 'get_' prefix and READ verb 'GET' confirm it queries historical network data without modification.
Attacks that exploit this kind of access
The rule that runs get_networks_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_networks_history, this is the rule to start with:
get_networks_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect REI Crypto MCP Server, apply this rule, and every get_networks_history call is checked against it from then on.
Questions about get_networks_history
GET /networks/history/{chain}. 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_networks_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.
get_networks_history 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_networks_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.
Set action: deny in the PolicyLayer policy for get_networks_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.
get_networks_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.
More on REI Crypto MCP Server, and thousands of servers like it.
This server
Across the catalogue