get_ml_signal
Get ML ensemble signal (5 models) — direction, probability, confidence. $0.05
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-ml-signal.md
What get_ml_signal does on Crypto Intelligence
AI agents call get_ml_signal 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 | — | Coin symbol (BTC, ETH, SOL, TAO, KAS, XLM) |
Parameters from the server's own tool schema.
Why get_ml_signal is rated Low
This tool retrieves pre-computed ML model outputs (direction, probability, confidence scores) with no side effects, no data modification, and no execution of arbitrary code. It is a read-only query for trading intelligence signals. The micropayment is a usage fee, not a financial operation category—the tool itself does not move user funds, execute trades, or create financial obligations.
From the tool's definition Tool name 'get_ml_signal' and description 'Get ML ensemble signal (5 models) — direction, probability, confidence' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_ml_signal 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_ml_signal, this is the rule to start with:
get_ml_signal 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_ml_signal call is checked against it from then on.
Questions about get_ml_signal
Get ML ensemble signal (5 models) — direction, probability, confidence. $0.05. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_ml_signal accepts 1 parameter: 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_ml_signal: 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_ml_signal 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_ml_signal 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_ml_signal. 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_ml_signal 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