coingecko-coin-history

Get a historical snapshot for a coin on a specific date (DD-MM-YYYY).

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/coingecko-coin-history.md

WHAT IT DOES

What coingecko-coin-history does on Meta Data Mcp

AI agents call coingecko-coin-history to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why coingecko-coin-history is rated Low

This tool queries open financial data (cryptocurrency prices) from the CoinGecko API without modifying, executing operations, or moving money. It is a simple data retrieval operation against a public API. The low severity reflects that misuse would only expose historical price information already publicly available, with no destructive or financial transaction capability.

From the tool's definition The tool 'coingecko-coin-history' retrieves historical data for a coin on a specific date. The verb 'get' and the function of querying a snapshot of past data indicate a read-only operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs coingecko-coin-history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coingecko-coin-history, this is the rule to start with:

coingecko-coin-history Allowed

coingecko-coin-history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "coingecko-coin-history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every coingecko-coin-history call is checked against it from then on.

FAQ

Questions about coingecko-coin-history

What does the coingecko-coin-history tool do? +

Get a historical snapshot for a coin on a specific date (DD-MM-YYYY). It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on coingecko-coin-history? +

Register the Meta Data MCP server in PolicyLayer and add a rule for coingecko-coin-history: 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 Meta Data Mcp. Nothing to install.

What risk level is coingecko-coin-history? +

coingecko-coin-history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit coingecko-coin-history? +

Yes. Add a rate_limit block to the coingecko-coin-history 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.

How do I block coingecko-coin-history completely? +

Set action: deny in the PolicyLayer policy for coingecko-coin-history. 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.

What MCP server provides coingecko-coin-history? +

coingecko-coin-history is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →