cmc_trending
Get trending cryptocurrencies from CoinMarketCap.
This record as markdown: /tools/creativelead-unclick/cmc-trending.md
What cmc_trending does on UnClick
AI agents call cmc_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why cmc_trending is rated Low
This tool retrieves cryptocurrency market trend data from an external service. It performs a read-only query with no ability to modify, delete, or execute actions. While it relates to financial markets, it does not itself move money, commit financial obligations, or execute trades — it only fetches informational data.
From the tool's definition Tool description states 'Get trending cryptocurrencies from CoinMarketCap' — a query operation that retrieves data without side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs cmc_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 cmc_trending, this is the rule to start with:
cmc_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 cmc_trending call is checked against it from then on.
Questions about cmc_trending
Get trending cryptocurrencies from CoinMarketCap. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cmc_trending accepts 2 parameters: limit, api_key. 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 cmc_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.
cmc_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 cmc_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 cmc_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.
cmc_trending 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