run_strategy_test
Run strategy backtest — win rate, Sharpe ratio, max drawdown. Strategies: analyst_v3, funding_monitor, ml_ensemble. $0.50
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/run-strategy-test.md
What run_strategy_test does on Crypto Intelligence
AI agents invoke run_strategy_test to trigger actions in Crypto Intelligence. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
coin | string | — | Coin to backtest (BTC, ETH, SOL) |
days | integer | — | Backtest period in days (7-365) |
strategy | string | — | Strategy: analyst_v3, funding_monitor, ml_ensemble |
Parameters from the server's own tool schema.
Why run_strategy_test is rated High
This tool executes backtesting logic on trading strategies, which is a computational operation with effects dependent on which strategy is selected and test parameters provided. While it does not directly move money (hence not Financial), it executes code/logic that simulates trading outcomes.
From the tool's definition Tool runs (executes) a strategy backtest with specified parameters returning financial metrics (win rate, Sharpe ratio, max drawdown). The verb 'run' combined with 'backtest' indicates computational execution of predefined trading strategies.
Attacks that exploit this kind of access
The rule that runs run_strategy_test 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 run_strategy_test, this is the rule to start with:
run_strategy_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 run_strategy_test call is checked against it from then on.
Questions about run_strategy_test
Run strategy backtest — win rate, Sharpe ratio, max drawdown. Strategies: analyst_v3, funding_monitor, ml_ensemble. $0.50. It is categorised as a Execute tool in the Crypto Intelligence MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_strategy_test accepts 3 parameters: coin, days, strategy. 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 run_strategy_test: 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.
run_strategy_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_strategy_test 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 run_strategy_test. 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.
run_strategy_test 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.
Across the catalogue