This record as markdown: /tools/creativelead-unclick/cmc-info.md
What cmc_info does on UnClick
AI agents call cmc_info 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 | — | |
symbol | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why cmc_info is rated Low
This tool performs a read-only query to fetch static cryptocurrency information. There is no capability to modify data, execute code, delete records, or trigger financial transactions. The metadata retrieved (prices, details, stats) would be of informational value only. Misuse by an AI agent would have minimal blast radius — at worst, excessive API calls or rate limiting.
From the tool's definition Tool retrieves cryptocurrency metadata from CoinMarketCap. The description indicates data retrieval with 'Get' and 'metadata' — no modification, deletion, or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs cmc_info 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_info, this is the rule to start with:
cmc_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 UnClick, apply this rule, and every cmc_info call is checked against it from then on.
Questions about cmc_info
Get cryptocurrency metadata from CoinMarketCap. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cmc_info accepts 3 parameters: id, symbol, 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_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 UnClick. Nothing to install.
cmc_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 cmc_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 cmc_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.
cmc_info 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