Risk controls
Built to lose small —or not at all.
A 30-day trial doesn’t make a bot safe; the limits do. Every trade is capped before it opens, and the patterns that blow accounts — martingale, grids, averaging down — are structurally impossible here.
- Stop-loss on every trade
- Stops after 3 losses
- One position at a time
The number that keeps a bad day small
3%
daily-loss floor
New trades stop when the day’s loss would cross 3% of your balance. The limit is a percentage, so it holds on any account size.
The hard limits
Every cap is enforced in code,before an order is sent.
These aren’t settings you hope hold. They’re checks the software is designed to enforce on the server and, where noted, locally in your own MetaTrader executor.
- Stop-loss
- Every tradeThe engine refuses to open any trade without a stop-loss attached. There is no code path that places an order without one — it fails closed.
- Risk per trade
- ≈0.3%Each trade risks roughly 0.3% of your account balance — a percentage, not a flat dollar amount. It scales with your account and never grows after a loss.
- Overall floor
- 10%A maximum-loss floor of 10%, trailing at your account’s peak, blocks any new entry that would breach it.
- Loss-streak halt
- 3 lossesAfter three losing trades in a day, the bot locks itself out for the rest of the day. A rough day can’t spiral.
- Open positions
- 1 maxNever more than a single open trade — enforced in four independent places, including locally inside the executor. It cannot stack trades or average down.
- Spread guard
- GatedA new entry is refused when the spread blows out past a set threshold — checked both on the server and locally in the executor.
- Trade count
- CappedHard caps on trades per day and per session lock out further entries once reached, so it never over-trades a session.
By design
What the bot can neverdo to your account.
The account-killers, ruled out at the structural level — not by policy, but by how the code is built.
- Use martingale — position size never increases after a loss
- Use a grid or average down into a losing position
- Open a second trade while one is already running
- Place a trade without a stop-loss
- Widen or drop a stop-loss to force an entry in
- Open a new trade while the server is unreachable
When something breaks
Disconnects, crashes,and outages.
The failure mode is always the same: open nothing new, and leave your existing stop-loss and take-profit exactly where they are, at your broker.
Server unreachable
Fails closedThe executor needs a valid decision to act. If it can’t reach the engine, it opens nothing new — and any open trade keeps the stop-loss and take-profit already at your broker.
App or MT5 closed
Fails closedNo new trades can open. Existing positions rest on their broker-side stop-loss and take-profit, exactly where they were.
Internet drops
Fails closedSame as above — no new entries, and your open trade’s stop and target live at the broker, not on your PC.
Licence lapses · switched off
Fails closedNew entries stop within about a minute. Any open position keeps its stop and target; renewal or switching ON resumes trading.
Where these limits live — honestly.
The stop-loss requirement, position sizing, and the daily and overall loss floors are enforced by the strategy engine on the server. Your own MetaTrader executor independently enforces the spread guard, the one-position rule, and your broker’s volume and stop-distance limits — and if it can’t reach the server, it simply opens nothing new. The executor trusts the server for the sizing and loss-floor decisions; it is not a fully independent risk brain, and we won’t claim it is.
RSForex Bot is trading software, not investment advice. Risk controls are designed to enforce limits; they do not guarantee a profit, prevent every loss, or guarantee any prop-firm challenge outcome. Trading gold carries risk, and you can lose money.
Risk controls
See the limits workon your own account.
Start a trial and watch the caps enforce themselves in your own MetaTrader — with a switch that stops new trades the instant you flip it. Or read the FAQ first.