crypto.coin-history

Historical market chart for a coin by CoinGecko id: time-series of price, market cap, and volume over the last N days (1-365) in USD or another vs-currency. Granularity is auto-selected by range (hourly for short windows, daily for long). For backtests, charts, and trend analysis.

SERVERMcp SOURCE@2sio/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-2s-io-mcp/crypto.coin-history.md

WHAT IT DOES

What crypto.coin-history does on Mcp

AI agents call crypto.coin-history to retrieve information from 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 crypto.coin-history is rated Low

This tool queries and retrieves historical cryptocurrency market data from CoinGecko without creating, modifying, deleting, or executing operations. It has no side effects on data or systems. The severity is low because even if misused by an agent, it only reads public market data and cannot cause harm, financial transactions, or system impact.

From the tool's definition Tool retrieves 'historical market chart' data as 'time-series of price, market cap, and volume' with no modification capability stated. Explicitly described for 'backtests, charts, and trend analysis' — passive consumption use cases.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crypto.coin-history safely

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

crypto.coin-history Allowed

crypto.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": {
    "crypto.coin-history": {}
  }
}

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

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

FAQ

Questions about crypto.coin-history

What does the crypto.coin-history tool do? +

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

Register the MCP server in PolicyLayer and add a rule for crypto.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 Mcp. Nothing to install.

What risk level is crypto.coin-history? +

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

Can I rate-limit crypto.coin-history? +

Yes. Add a rate_limit block to the crypto.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 crypto.coin-history completely? +

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

crypto.coin-history is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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