get_proven_record
Verifiable prop-firm trading results from our own ML-driven strategy: passed $100k FTMO challenge 2026-04-17 with +5.04% return in 5 days, 16 BTC-long trades, 81.25% win rate. $0.50
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-proven-record.md
What get_proven_record does on Crypto Intelligence
AI agents call get_proven_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.
Why get_proven_record is rated Low
This tool queries and retrieves past trading performance records. It is a data lookup operation with no side effects—it does not execute trades, transfer funds, delete data, or modify state. The $0.50 cost is a micropayment for the API call, not a financial transaction moving assets. The tool provides analytics/reporting, which is a Read operation.
From the tool's definition Tool name 'get_proven_record' and description indicate retrieval of historical trading results data ('Verifiable prop-firm trading results', 'passed $100k FTMO challenge', trading statistics).
Attacks that exploit this kind of access
The rule that runs get_proven_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_proven_record, this is the rule to start with:
get_proven_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_proven_record call is checked against it from then on.
Questions about get_proven_record
Verifiable prop-firm trading results from our own ML-driven strategy: passed $100k FTMO challenge 2026-04-17 with +5.04% return in 5 days, 16 BTC-long trades, 81.25% win rate. $0.50. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_proven_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_proven_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_proven_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_proven_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_proven_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