crypto_history
Historical OHLCV candles (open, high, low, close, volume) via CoinGecko for backtesting, training, and performance analy Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/com-gocreativeai-omnicall-agent-tools/crypto-history.md
What crypto_history does on Omnicall — Agent Tools Gateway
AI agents call crypto_history to retrieve information from Omnicall — Agent Tools Gateway 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 |
|---|---|---|---|
arg | string | Yes |
Parameters from the server's own tool schema.
Why crypto_history is rated Low
This tool only fetches historical cryptocurrency market data. It has no side effects: it does not execute trades, modify data, delete records, run arbitrary code, or move funds. Although the server context mentions financial capabilities (crypto/DeFi/markets) and uses a pay-per-call model, this specific tool itself is a pure data retrieval operation.
From the tool's definition Tool retrieves 'Historical OHLCV candles (open, high, low, close, volume) via CoinGecko' — a query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs crypto_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omnicall — Agent Tools Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto_history, this is the rule to start with:
crypto_history 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 Omnicall — Agent Tools Gateway, apply this rule, and every crypto_history call is checked against it from then on.
Questions about crypto_history
Historical OHLCV candles (open, high, low, close, volume) via CoinGecko for backtesting, training, and performance analy Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the Omnicall — Agent Tools Gateway MCP Server, which means it retrieves data without modifying state.
crypto_history accepts 1 parameter: arg. Required: arg. The full parameter table on this page comes from the server's own tool schema.
Register the Omnicall — Agent Tools Gateway MCP server in PolicyLayer and add a rule for crypto_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 Omnicall — Agent Tools Gateway. Nothing to install.
crypto_history 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 crypto_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.
Set action: deny in the PolicyLayer policy for crypto_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.
crypto_history is provided by the Omnicall — Agent Tools Gateway MCP server (https://omnicall.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omnicall — Agent Tools Gateway, and thousands of servers like it.
This server
Across the catalogue