crypto_coin_history
Get historical price data for a cryptocurrency from CoinGecko.
This record as markdown: /tools/creativelead-unclick/crypto-coin-history.md
What crypto_coin_history does on UnClick
AI agents call crypto_coin_history to retrieve information from UnClick 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 |
|---|---|---|---|
id | string | — | |
date | string | — | DD-MM-YYYY |
Parameters from the server's own tool schema.
Why crypto_coin_history is rated Low
This is a read-only operation that fetches historical cryptocurrency price data from a public API (CoinGecko). It does not modify, delete, or execute any state-changing operations. The tool only retrieves information, making it a Read category with low severity since misuse would only result in excessive data retrieval rather than financial transactions or destructive actions.
From the tool's definition The tool 'Get historical price data for a cryptocurrency from CoinGecko' retrieves and queries historical price information with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs crypto_coin_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_coin_history, this is the rule to start with:
crypto_coin_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 UnClick, apply this rule, and every crypto_coin_history call is checked against it from then on.
Questions about crypto_coin_history
Get historical price data for a cryptocurrency from CoinGecko. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
crypto_coin_history accepts 2 parameters: id, date. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for crypto_coin_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 UnClick. Nothing to install.
crypto_coin_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 crypto_coin_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 crypto_coin_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.
crypto_coin_history is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue