crypto_price_historical

Get historical daily price data for a cryptocurrency. Optionally filter by date range.

SERVERNodebench SOURCEnodebench-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about crypto_price_historical

What does the crypto_price_historical tool do? +

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.

How do I enforce a policy on crypto_price_historical? +

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.

What risk level is crypto_price_historical? +

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

Can I rate-limit crypto_price_historical? +

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.

How do I block crypto_price_historical completely? +

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.

What MCP server provides crypto_price_historical? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.