get_track_record
Get verified ML prediction track record — accuracy, win rate, historical predictions with outcomes. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-track-record.md
What get_track_record does on Crypto Intelligence
AI agents call get_track_record 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 |
|---|---|---|---|
days | integer | — | History days (1-365) |
Parameters from the server's own tool schema.
Why get_track_record is rated Low
This tool retrieves and queries historical prediction performance metrics and outcomes. It performs no write operations, does not execute trades or external commands, and does not delete or modify data. The $0.005 micropayment is merely a usage fee, not a financial transaction on behalf of the user. This is a pure data retrieval operation.
From the tool's definition Tool name 'get_track_record' and description 'Get verified ML prediction track record — accuracy, win rate, historical predictions with outcomes' indicate retrieval of historical data and analytics with no modification, deletion, or execution of trades.
Attacks that exploit this kind of access
The rule that runs get_track_record 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_track_record, this is the rule to start with:
get_track_record 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_track_record call is checked against it from then on.
Questions about get_track_record
Get verified ML prediction track record — accuracy, win rate, historical predictions with outcomes. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_track_record accepts 1 parameter: days. 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_track_record: 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_track_record 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_track_record 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_track_record. 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_track_record 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