crypto_compare
Compare 2-5 cryptocurrencies side by side. Shows price, 24-hour change, market cap, volume, and rank for each coin in a comparison table. Use this for 'compare bitcoin and ethereum', 'BTC vs ETH vs SOL', 'which is bigger bitcoin or ethereum?', 'compare top cryptos', 'crypto head to head', or any ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/crypto-compare.md
What crypto_compare does on Livedatalink
AI agents call crypto_compare to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
coins | object | Yes | Coin names or tickers, 2-5 coins. Accept either CSV string ('bitcoin,ethereum,solana') or array (['bitcoin','ethereum','solana']). |
Parameters from the server's own tool schema.
Why crypto_compare is rated Low
This tool retrieves and displays real-time cryptocurrency comparison data. It has no side effects: it does not execute transactions, modify data, delete data, or trigger external operations. The user cannot perform financial transactions (buy/sell/trade), execute code, or alter any state.
From the tool's definition The tool 'Compare 2-5 cryptocurrencies side by side. Shows price, 24-hour change, market cap, volume, and rank' performs data retrieval and display operations only.
Attacks that exploit this kind of access
The rule that runs crypto_compare safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_compare, this is the rule to start with:
crypto_compare 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 Livedatalink, apply this rule, and every crypto_compare call is checked against it from then on.
Questions about crypto_compare
Compare 2-5 cryptocurrencies side by side. Shows price, 24-hour change, market cap, volume, and rank for each coin in a comparison table. Use this for 'compare bitcoin and ethereum', 'BTC vs ETH vs SOL', 'which is bigger bitcoin or ethereum?', 'compare top cryptos', 'crypto head to head', or any multi-coin comparison question. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
crypto_compare accepts 1 parameter: coins. Required: coins. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for crypto_compare: 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 Livedatalink. Nothing to install.
crypto_compare 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_compare 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_compare. 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_compare is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue