coinlore_tickers
List top cryptocurrency tickers with price and market cap from Coinlore.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/coinlore-tickers.md
What coinlore_tickers does on UnClick
AI agents call coinlore_tickers 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 | — | Max results (default 20, max 100). |
start | number | — | Offset for pagination (default 0). |
Parameters from the server's own tool schema.
Why coinlore_tickers is rated Low
This tool retrieves cryptocurrency market information (tickers, prices, market cap) from an external source. It has no side effects, does not execute code, does not modify data, and does not move money or create financial obligations. While the data relates to financial assets, the tool itself only reads/fetches public market data without any transactional capability.
From the tool's definition Tool description states 'List top cryptocurrency tickers with price and market cap from Coinlore' — this is a retrieval operation that queries and returns financial market data without modifying anything.
Attacks that exploit this kind of access
The rule that runs coinlore_tickers 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 coinlore_tickers, this is the rule to start with:
coinlore_tickers 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 coinlore_tickers call is checked against it from then on.
Questions about coinlore_tickers
List top cryptocurrency tickers with price and market cap from Coinlore. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
coinlore_tickers accepts 2 parameters: limit, start. 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 coinlore_tickers: 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.
coinlore_tickers 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 coinlore_tickers 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 coinlore_tickers. 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.
coinlore_tickers 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