get_macro_corr
Get BTC-Macro correlations — rolling Pearson vs DXY, VIX, Treasury, Oil, Gold with regime signal. $0.03
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-macro-corr.md
What get_macro_corr does on Crypto Intelligence
AI agents call get_macro_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 |
|---|---|---|---|
window | integer | — | Correlation window in days (7 or 30) |
Parameters from the server's own tool schema.
Why get_macro_corr is rated Low
This tool queries and returns analytical data (Pearson correlations between BTC and macro indicators like DXY, VIX, Treasury yields, Oil, and Gold) with regime signals. It has no side effects—no data is created, modified, deleted, or executed. The financial micropayment is incidental to the data retrieval service, not a movement of funds.
From the tool's definition Tool name 'get_macro_corr' and description explicitly retrieve correlations ('Get BTC-Macro correlations') with no modification, deletion, or execution of external systems. The micropayment cost ($0.03) is for data access, not for state changes or operations.
Attacks that exploit this kind of access
The rule that runs get_macro_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_macro_corr, this is the rule to start with:
get_macro_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_macro_corr call is checked against it from then on.
Questions about get_macro_corr
Get BTC-Macro correlations — rolling Pearson vs DXY, VIX, Treasury, Oil, Gold with regime signal. $0.03. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_macro_corr accepts 1 parameter: window. 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_macro_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_macro_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_macro_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_macro_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_macro_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