get_trend
Trend analytics — ADX-14 strength classification (weak/moderate/strong/very_strong), direction (up/down/sideways) via DMP/DMN, OLS slope per day, regime duration in days, 30d suppo. $0.12
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-trend.md
What get_trend does on Crypto Intelligence
AI agents call get_trend 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_trend is rated Low
The tool retrieves and calculates trend metrics from crypto market data. It performs analysis and returns classification results without modifying underlying data, executing arbitrary code, or committing financial obligations. The $0.12 cost is a micropayment for the data/computation, not a financial transaction that moves money or creates obligations. This is a straightforward Read category tool.
From the tool's definition Tool description describes 'Trend analytics' with analysis outputs: 'ADX-14 strength classification', 'direction (up/down/sideways)', 'OLS slope per day', 'regime duration in days', '30d suppo[rt]'.
Attacks that exploit this kind of access
The rule that runs get_trend 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_trend, this is the rule to start with:
get_trend 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_trend call is checked against it from then on.
Questions about get_trend
Trend analytics — ADX-14 strength classification (weak/moderate/strong/very_strong), direction (up/down/sideways) via DMP/DMN, OLS slope per day, regime duration in days, 30d suppo. $0.12. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_trend 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_trend: 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_trend 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_trend 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_trend. 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_trend 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