coingecko_nft_category
CoinGecko NFT category. Returns normalized NFT collection rows from a CoinGecko public NFT category page. This endpoint supports the documented vs_currency enum.
This record as markdown: /tools/crawlora-mcp/coingecko-nft-category.md
What coingecko_nft_category does on Crawlora
AI agents call coingecko_nft_category to retrieve information from Crawlora 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 |
|---|---|---|---|
page | integer | — | Page number, default 1 |
slug | string | Yes | CoinGecko NFT category slug such as metaverse |
limit | integer | — | Rows to return, default 100, max 100 |
vs_currency | string | — | Quote currency |
Parameters from the server's own tool schema.
Why coingecko_nft_category is rated Low
Even though coingecko_nft_category only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs coingecko_nft_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coingecko_nft_category, this is the rule to start with:
coingecko_nft_category 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 Crawlora, apply this rule, and every coingecko_nft_category call is checked against it from then on.
Questions about coingecko_nft_category
CoinGecko NFT category. Returns normalized NFT collection rows from a CoinGecko public NFT category page. This endpoint supports the documented vs_currency enum. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
coingecko_nft_category accepts 4 parameters: page, slug, limit, vs_currency. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for coingecko_nft_category: 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 Crawlora. Nothing to install.
coingecko_nft_category 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 coingecko_nft_category 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 coingecko_nft_category. 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.
coingecko_nft_category is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue