strategy_backtest
Backtest simple indicator-driven trading strategies on MT5 candle history.
This record as markdown: /tools/emerzon-mt-data-mcp/strategy-backtest.md
What strategy_backtest does on MetaTrader5 MCP Server
AI agents invoke strategy_backtest to trigger actions in MetaTrader5 MCP Server. 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.
Why strategy_backtest is rated High
Backtesting executes a strategy engine over historical candle data, which is a computational execution operation. While it operates on historical data and does not place live trades, it triggers complex execution logic (indicator calculations, simulated order placement/management).
From the tool's definition 'Backtest simple indicator-driven trading strategies on MT5 candle history' — runs a simulation/execution process against historical data using trading strategy logic
Attacks that exploit this kind of access
The rule that runs strategy_backtest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MetaTrader5 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For strategy_backtest, this is the rule to start with:
strategy_backtest 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 MetaTrader5 MCP Server, apply this rule, and every strategy_backtest call is checked against it from then on.
Questions about strategy_backtest
Backtest simple indicator-driven trading strategies on MT5 candle history. It is categorised as a Execute tool in the MetaTrader5 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MetaTrader5 MCP Server MCP server in PolicyLayer and add a rule for strategy_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 MetaTrader5 MCP Server. Nothing to install.
strategy_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 strategy_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 strategy_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.
strategy_backtest is provided by the MetaTrader5 MCP Server MCP server (emerzon/mt-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MetaTrader5 MCP Server, and thousands of servers like it.
Across the catalogue