get_intel_history
Historical intelligence — OHLCV, funding rates, OI, signals with configurable lookback. 730d available. $0.01
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-intel-history.md
What get_intel_history does on Crypto Intelligence
AI agents call get_intel_history to retrieve information from Crypto Intelligence 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 |
|---|---|---|---|
coin | string | — | Coin symbol (e.g. BTC) |
hours | integer | — | Lookback hours (1-720) |
include | string | — | Data types: ohlcv,funding,oi,signals |
Parameters from the server's own tool schema.
Why get_intel_history is rated Low
This tool retrieves historical market data and derived analytics. It performs no writes, executions, deletions, or financial transactions—merely queries and returns information. The configurable lookback parameter allows flexible data retrieval but does not modify underlying state. Confidence is high because the description and pricing model align with a pure read/query operation.
From the tool's definition Tool name 'get_intel_history' and description 'Historical intelligence — OHLCV, funding rates, OI, signals with configurable lookback' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_intel_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_intel_history, this is the rule to start with:
get_intel_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 Crypto Intelligence, apply this rule, and every get_intel_history call is checked against it from then on.
Questions about get_intel_history
Historical intelligence — OHLCV, funding rates, OI, signals with configurable lookback. 730d available. $0.01. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_intel_history accepts 3 parameters: coin, hours, include. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_intel_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 Crypto Intelligence. Nothing to install.
get_intel_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 get_intel_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 get_intel_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.
get_intel_history is provided by the Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue