forecast_backtest_run
Rolling-origin backtest over historical anchors using the forecast tool.
This record as markdown: /tools/emerzon-mt-data-mcp/forecast-backtest-run.md
What forecast_backtest_run does on MetaTrader5 MCP Server
AI agents invoke forecast_backtest_run 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 forecast_backtest_run is rated High
Execute is appropriate because the tool runs a computational workflow (backtesting algorithm) that processes data and produces outputs dependent on user-supplied parameters. It does not directly move money (not Financial), does not delete data (not Destructive), and does not simply retrieve static data (not Read).
From the tool's definition The tool performs 'rolling-origin backtest over historical anchors using the forecast tool.' Backtesting executes trading strategies against historical data with computational side effects (model fitting, signal generation, performance metrics).
Attacks that exploit this kind of access
The rule that runs forecast_backtest_run 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 forecast_backtest_run, this is the rule to start with:
forecast_backtest_run 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 forecast_backtest_run call is checked against it from then on.
Questions about forecast_backtest_run
Rolling-origin backtest over historical anchors using the forecast tool. 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 forecast_backtest_run: 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.
forecast_backtest_run 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 forecast_backtest_run 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 forecast_backtest_run. 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.
forecast_backtest_run 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