get_oi_history
Open Interest time series for any tracked coin across Binance + Bybit + OKX. Hourly buckets up to 60 days. Per-exchange breakdown + total + price. Stats: min/max/avg/current total USD and 30-day change_pct. $0.05
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-oi-history.md
What get_oi_history does on Crypto Intelligence
AI agents call get_oi_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 | Yes | Coin symbol |
days | integer | — | Look-back days (1-60) |
Parameters from the server's own tool schema.
Why get_oi_history is rated Low
This is a straightforward data retrieval tool that queries Open Interest analytics across exchanges. It has no side effects, creates no resources, executes no code, and does not move funds. The $0.05 cost is a micropayment for the service, not a financial transaction executed by the tool itself. Low severity because misuse (e.g., querying repeatedly) is rate-limited by cost and causes only informational leakage.
From the tool's definition Tool retrieves historical Open Interest time series data ("time series for any tracked coin", "hourly buckets", "per-exchange breakdown"). Returns analytics metrics (min/max/avg/current, 30-day change).
Attacks that exploit this kind of access
The rule that runs get_oi_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_oi_history, this is the rule to start with:
get_oi_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_oi_history call is checked against it from then on.
Questions about get_oi_history
Open Interest time series for any tracked coin across Binance + Bybit + OKX. Hourly buckets up to 60 days. Per-exchange breakdown + total + price. Stats: min/max/avg/current total USD and 30-day change_pct. $0.05. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_oi_history accepts 2 parameters: coin, days. Required: coin. 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_oi_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_oi_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_oi_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_oi_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_oi_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