crypto_trending
Get trending cryptocurrencies from CoinGecko.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/crypto-trending.md
What crypto_trending does on UnClick
AI agents call crypto_trending 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.
Why crypto_trending is rated Low
This tool retrieves market data from an external API (CoinGecko) without side effects. It neither executes code, modifies data, deletes records, nor initiates financial transactions. An AI agent misusing this tool poses minimal risk—the worst outcome would be excessive API calls or using stale data for poor decisions, neither of which causes direct harm. Classification as Read is appropriate.
From the tool's definition Tool name 'crypto_trending' and description 'Get trending cryptocurrencies from CoinGecko' indicate a query/retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs crypto_trending 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_trending, this is the rule to start with:
crypto_trending 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_trending call is checked against it from then on.
Questions about crypto_trending
Get trending cryptocurrencies from CoinGecko. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for crypto_trending: 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_trending 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_trending 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_trending. 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_trending is provided by the UnClick MCP server (@unclick/mcp-server). 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