get_beta_to_btc
Beta coefficient of coin vs BTC via OLS regression on 4h returns + rolling 30d stability analysis. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-beta-to-btc.md
What get_beta_to_btc does on Crypto Intelligence
AI agents call get_beta_to_btc 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 (BTC, ETH, etc.) |
Parameters from the server's own tool schema.
Why get_beta_to_btc is rated Low
This tool retrieves and calculates financial metrics (beta coefficient via OLS regression on historical returns). It is purely analytical—it reads historical price data, performs statistical computation, and returns the result. There are no side effects, data modifications, code execution, or financial transactions. The $0.10 micropayment is a standard API fee, not a financial obligation created by the tool itself.
From the tool's definition Tool name 'get_beta_to_btc' and description 'Beta coefficient of coin vs BTC via OLS regression on 4h returns + rolling 30d stability analysis' indicate a calculation and retrieval of statistical/analytical data.
Attacks that exploit this kind of access
The rule that runs get_beta_to_btc 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_beta_to_btc, this is the rule to start with:
get_beta_to_btc 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_beta_to_btc call is checked against it from then on.
Questions about get_beta_to_btc
Beta coefficient of coin vs BTC via OLS regression on 4h returns + rolling 30d stability analysis. $0.10. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_beta_to_btc accepts 1 parameter: coin. 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_beta_to_btc: 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_beta_to_btc 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_beta_to_btc 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_beta_to_btc. 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_beta_to_btc 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