get_regime_history
HMM market-regime timeline — accumulation, markup, distribution, markdown, high_volatility per timestamp with confidence. transitions_only returns only regime-change events for strategy-trigger research. $0.05
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-regime-history.md
What get_regime_history does on Crypto Intelligence
AI agents call get_regime_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 |
|---|---|---|---|
days | integer | — | Look-back days (1-90) |
transitions_only | boolean | — | Only regime-change events |
Parameters from the server's own tool schema.
Why get_regime_history is rated Low
This is a data retrieval tool that returns pre-computed market regime classifications and transition events. It has no side effects, does not execute trades, does not modify data, and does not delete anything. The transitions_only parameter filters the results but does not change the fundamental read-only nature.
From the tool's definition Tool retrieves historical market regime data ('HMM market-regime timeline') with classifications per timestamp. No mutation, deletion, or financial transaction—purely informational query of historical analysis.
Attacks that exploit this kind of access
The rule that runs get_regime_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_regime_history, this is the rule to start with:
get_regime_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_regime_history call is checked against it from then on.
Questions about get_regime_history
HMM market-regime timeline — accumulation, markup, distribution, markdown, high_volatility per timestamp with confidence. transitions_only returns only regime-change events for strategy-trigger research. $0.05. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_regime_history accepts 2 parameters: days, transitions_only. 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_regime_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_regime_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_regime_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_regime_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_regime_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