New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

strategy_backtest

Backtest simple indicator-driven trading strategies on MT5 candle history.

SERVERMetaTrader5 MCP Server SOURCEemerzon/mt-data-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about strategy_backtest

What does the strategy_backtest tool do? +

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.

How do I enforce a policy on strategy_backtest? +

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.

What risk level is strategy_backtest? +

strategy_backtest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit strategy_backtest? +

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.

How do I block strategy_backtest completely? +

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.

What MCP server provides strategy_backtest? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MetaTrader5 MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.