AI agents invoke run_backtest to trigger actions in Ai Trader. 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.
This tool executes algorithmic operations (backtest simulations) whose outcomes depend on arguments (strategy parameters, market data, time periods). Although not directly destructive or financial in itself, it triggers complex external computations and can influence downstream trading decisions.
From the tool's definition Tool name 'run_backtest' paired with server description stating it 'run backtests' and 'analyze trading algorithms.' Backtesting simulates execution of trading strategies on historical data, which is a computational operation with side effects (generating…
Attacks that exploit this kind of access
run_backtest. It is categorised as a Execute tool in the Ai Trader MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ai Trader MCP server in PolicyLayer and add a rule for run_backtest: 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 Ai Trader. Nothing to install.
run_backtest 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_backtest 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_backtest. 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_backtest is provided by the Ai Trader MCP server (whchien/ai-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.