crypto_info
Get a detailed profile for any cryptocurrency including description, market data, supply info, all-time high/low, genesis date, blockchain, categories, and website links. Use this for 'tell me about bitcoin', 'what is ethereum?', 'solana info', 'describe cardano', 'crypto profile', 'coin details'...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/crypto-info.md
What crypto_info does on Livedatalink
AI agents call crypto_info 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 |
|---|---|---|---|
coin | string | Yes | Cryptocurrency name or ticker (e.g., 'bitcoin', 'BTC', 'ethereum') |
Parameters from the server's own tool schema.
Why crypto_info is rated Low
This tool retrieves and presents public cryptocurrency market information. It performs no create, modify, delete, or execute operations. The data returned (market data, supply info, genesis date, blockchain info) is already publicly available information being queried, not generated or altered. This is a straightforward read/query operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] a detailed profile' with 'description, market data, supply info' and is used for queries like 'tell me about bitcoin' and 'coin details'.
Attacks that exploit this kind of access
The rule that runs crypto_info 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_info, this is the rule to start with:
crypto_info 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_info call is checked against it from then on.
Questions about crypto_info
Get a detailed profile for any cryptocurrency including description, market data, supply info, all-time high/low, genesis date, blockchain, categories, and website links. Use this for 'tell me about bitcoin', 'what is ethereum?', 'solana info', 'describe cardano', 'crypto profile', 'coin details', or any question asking for background information about a specific cryptocurrency project. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
crypto_info accepts 1 parameter: coin. Required: coin. 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_info: 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_info 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_info 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_info. 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_info 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