get_factor_analytics
Factor decomposition across 4 dimensions: Momentum (30d return normalized by 90d vol), Carry (annualized funding rate), Crowding (OI-delta vs. $0.15
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-factor-analytics.md
What get_factor_analytics does on Crypto Intelligence
AI agents call get_factor_analytics 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_factor_analytics is rated Low
This tool queries and retrieves pre-computed financial analytics and factor decomposition data. It performs no state changes, does not execute trades or financial transactions, does not run code, and does not delete data. The description is cut off but clearly indicates passive data retrieval of market analysis metrics.
From the tool's definition Tool name 'get_factor_analytics' and description indicate data retrieval: 'Factor decomposition across 4 dimensions: Momentum', 'Carry', 'Crowding'. Uses 'get_' prefix (standard read pattern).
Attacks that exploit this kind of access
The rule that runs get_factor_analytics 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_factor_analytics, this is the rule to start with:
get_factor_analytics 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_factor_analytics call is checked against it from then on.
Questions about get_factor_analytics
Factor decomposition across 4 dimensions: Momentum (30d return normalized by 90d vol), Carry (annualized funding rate), Crowding (OI-delta vs. $0.15. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_factor_analytics 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_factor_analytics: 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_factor_analytics 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_factor_analytics 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_factor_analytics. 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_factor_analytics 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