get_rolling_corr
Rolling Pearson correlation between two coins over configurable window (7-90d). $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-rolling-corr.md
What get_rolling_corr does on Crypto Intelligence
AI agents call get_rolling_corr 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 |
|---|---|---|---|
pair | string | Yes | Pair format BASE-QUOTE (e.g. BTC-ETH) |
Parameters from the server's own tool schema.
Why get_rolling_corr is rated Low
The tool retrieves and calculates correlation metrics from historical price data. It has no side effects—it neither creates, modifies, deletes data, nor executes arbitrary code or financial transactions (the $0.10 is a query cost, not a financial operation). The configurable window is a safe input parameter for historical analysis. This is clearly a Read operation (analyze/compute).
From the tool's definition Tool computes and returns 'rolling Pearson correlation between two coins over configurable window'. This is a statistical calculation/query operation with no data modification, deletion, or external state changes.
Attacks that exploit this kind of access
The rule that runs get_rolling_corr 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_rolling_corr, this is the rule to start with:
get_rolling_corr 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_rolling_corr call is checked against it from then on.
Questions about get_rolling_corr
Rolling Pearson correlation between two coins over configurable window (7-90d). $0.10. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_rolling_corr accepts 1 parameter: pair. Required: pair. 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_rolling_corr: 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_rolling_corr 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_rolling_corr 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_rolling_corr. 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_rolling_corr 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