Returns all static metadata for one or more cryptocurrencies including logo, description, and website URLs.
AI agents call getCryptoMetadata to retrieve information from CoinMarketCap MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches static, read-only metadata (logo, description, website URLs) about cryptocurrencies. It performs no writes, deletions, code execution, or financial transactions. The data returned is informational and immutable from the tool's perspective. Risk is minimal; misuse by an AI agent would result in information disclosure only, not resource modification or financial impact.
From the tool's definition Tool name 'getCryptoMetadata' and description states it 'Returns all static metadata' — it retrieves and queries data with no side effects.
Documented attack patterns abuse exactly the kind of access getCryptoMetadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CoinMarketCap MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getCryptoMetadata:
{
"version": "1",
"default": "deny",
"tools": {
"getCryptoMetadata": {}
}
}getCryptoMetadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns all static metadata for one or more cryptocurrencies including logo, description, and website URLs. It is categorised as a Read tool in the CoinMarketCap MCP MCP Server, which means it retrieves data without modifying state.
Register the CoinMarketCap MCP server in PolicyLayer and add a rule for getCryptoMetadata: 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 CoinMarketCap MCP. Nothing to install.
getCryptoMetadata 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 getCryptoMetadata 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 getCryptoMetadata. 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.
getCryptoMetadata is provided by the CoinMarketCap MCP server (shinzo-labs/coinmarketcap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 CoinMarketCap MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 CoinMarketCap MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.