get_signal_accuracy
Historical directional accuracy of our ML signal models for a specific coin, built from resolved shadow predictions. $0.10
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-signal-accuracy.md
What get_signal_accuracy does on Crypto Intelligence
AI agents call get_signal_accuracy 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_signal_accuracy is rated Low
This tool retrieves historical performance metrics and analytics data about ML models. It is a read-only query with no side effects, reversible operations, code execution, or financial commitments. The micropayment is incidental billing for data access, not a financial operation that transfers value or creates obligations beyond the query itself.
From the tool's definition Tool name 'get_signal_accuracy' and description 'Historical directional accuracy of our ML signal models for a specific coin, built from resolved shadow predictions' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_signal_accuracy 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_signal_accuracy, this is the rule to start with:
get_signal_accuracy 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_signal_accuracy call is checked against it from then on.
Questions about get_signal_accuracy
Historical directional accuracy of our ML signal models for a specific coin, built from resolved shadow predictions. $0.10. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_signal_accuracy 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_signal_accuracy: 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_signal_accuracy 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_signal_accuracy 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_signal_accuracy. 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_signal_accuracy 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