High Risk →

run_backtest

Run a backtest on an Expert Advisor

How to control run_backtest ↓

What run_backtest does on MCP MetaTrader 4 Server

AI agents invoke run_backtest to trigger actions in MCP MetaTrader 4 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.

High Risk

Why run_backtest needs a policy

This tool triggers execution of trading strategy code (Expert Advisors) against historical market data. While backtesting is non-destructive and does not commit real trades or modify live data, it executes arbitrary user-provided trading algorithms.

From the tool's definition Tool is named 'run_backtest' with description 'Run a backtest on an Expert Advisor'. The verb 'Run' indicates execution of code/algorithms.

Documented attack patterns abuse exactly the kind of access run_backtest gives an agent:

How to control run_backtest

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MetaTrader 4 Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_backtest:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_backtest": {
      "limits": [
        {
          "counter": "run_backtest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_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.

  1. Create a free account and register MCP MetaTrader 4 Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about run_backtest

What does the run_backtest tool do? +

Run a backtest on an Expert Advisor. It is categorised as a Execute tool in the MCP MetaTrader 4 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 run_backtest? +

Register the MCP MetaTrader 4 Server 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 MCP MetaTrader 4 Server. Nothing to install.

What risk level is run_backtest? +

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

Can I rate-limit run_backtest? +

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.

How do I block run_backtest completely? +

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.

What MCP server provides run_backtest? +

run_backtest is provided by the MCP MetaTrader 4 Server MCP server (8nite/metatrader-4-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP MetaTrader 4 Server tool call.

Start from MCP MetaTrader 4 Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 MCP MetaTrader 4 Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.