crypto_price_historical
Get historical daily price data for a cryptocurrency. Optionally filter by date range.
This record as markdown: /tools/io-github-homenshum-nodebench/crypto-price-historical.md
What crypto_price_historical does on Nodebench
AI agents call crypto_price_historical to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crypto_price_historical is rated Low
This tool retrieves historical cryptocurrency price information—a read-only operation that queries existing data without modifying, deleting, or executing code. No financial transactions occur; it merely provides market data. Low severity because misuse would at worst return irrelevant price data, with no blast radius on systems or financial accounts.
From the tool's definition Tool name 'crypto_price_historical' and description 'Get historical daily price data for a cryptocurrency' indicate data retrieval with no side effects. The optional date range filter is a query parameter, not a destructive or transactional operation.
Attacks that exploit this kind of access
The rule that runs crypto_price_historical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_price_historical, this is the rule to start with:
crypto_price_historical 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 Nodebench, apply this rule, and every crypto_price_historical call is checked against it from then on.
Questions about crypto_price_historical
Get historical daily price data for a cryptocurrency. Optionally filter by date range. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for crypto_price_historical: 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 Nodebench. Nothing to install.
crypto_price_historical 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 crypto_price_historical 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 crypto_price_historical. 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.
crypto_price_historical is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue