Auto Close Trades at Daily Loss Limit: A Prop Trader's Setup Guide
Learn how to auto close trades at daily loss limit on MT5 before a prop firm breach costs you a funded account. Setup, cost, and timeline inside.

It's 2:47am in Dubai and a funded trader is asleep while three open positions on GBPJPY drift against them. By the time they check their phone at 6am, the account has blown through FTMO's daily loss limit by 0.3%. The challenge is over. Weeks of work, gone, because nothing was watching the account while they slept.
This happens constantly to prop-challenge takers and funded traders who manage risk manually or trust a broker-side stop that doesn't account for floating drawdown across multiple open trades. A single missed alert, a slow VPS, or a spread spike during news can turn a passing account into a failed one. The fix isn't more discipline — it's a system that doesn't sleep, doesn't hesitate, and doesn't negotiate with itself when equity is falling.
This guide covers what it actually takes to auto close trades at daily loss limit on MT5, the difference between doing it yourself and having it configured for you, what it costs, and how fast it can be live. For the productized version of this, see the Prop-Firm Guardian EA offer page from Bharat AI Saathi.
What Prop-Firm Guardian EA actually does
Prop-Firm Guardian EA is a rule-enforcing Expert Advisor for MetaTrader 5. It sits on the account alongside whatever strategy or signal-copy system the trader already runs, and it does one job continuously: monitor account equity, balance, and open positions against the exact numeric limits the client's prop firm enforces — FTMO, FundedNext, The5ers, or another firm with similar rule structures.
When floating or realized loss for the day approaches the configured threshold, the EA closes trades automatically at a soft-stop level set a small buffer before the firm's hard limit, so the account never actually touches the breach line. It also tracks maximum drawdown from the account's high-water mark, enforces a news blackout window around high-impact releases if the firm requires one, caps lot size per trade, and checks for "consistency rule" violations some firms apply (for example, no single day accounting for more than a set percentage of total profit).
Every action — a soft-stop close, an approaching-limit warning, a blocked oversized order — sends a Telegram or WhatsApp alert in real time, plus a daily P/L summary. It is not a trading strategy and does not place trades on its own. It is a guardrail around whatever the trader or their copier is already doing.
How it works, step by step
- Kickoff call or message. Client shares their prop firm name, account size, daily loss limit, max drawdown limit, and any consistency or news-trading restrictions from their firm's rulebook.
- Rule mapping. The team translates the firm's published rules into exact EA parameters — daily loss in both percentage and account currency, trailing vs. static drawdown, blackout windows.
- Soft-stop calibration. Soft-stop thresholds are set below the hard limit (commonly a buffer that accounts for slippage and spread widening) so the EA closes before, not at, the firm's line.
- VPS install. The EA is installed on the client's existing VPS, or a recommendation is given if they don't have one. MT5 terminal is configured to run continuously.
- Alert channel setup. Telegram or WhatsApp is connected for breach warnings, soft-stop notifications, and the daily summary.
- 15-minute walkthrough. A live screen-share where the trader sees a simulated approach to the loss limit and watches the EA respond, plus how to read alerts.
- Daily operation. The EA runs silently in the background. The trader trades normally; the EA only intervenes when a limit is actually being approached.
Trigger: Account equity drawdown reaches 4.2% against a 5% daily loss limit on a $100,000 FTMO account. Action: Guardian EA closes all open positions, cancels pending orders, and sends: "⚠️ Soft-stop triggered — FTMO daily loss buffer hit at 4.2%. All positions closed. Daily P/L: -$4,180. Trading disabled until server reset at 00:00 CET." Customer: "Did that save the account?" Agent: "Yes — the hard limit was 5.0% ($5,000). The close happened at 4.2% ($4,180), before the breach line."
Before and after
| Situation | Before | After |
|---|---|---|
| Trader asleep during a volatile Asian session | Positions run unmonitored until morning | EA closes at soft-stop threshold regardless of time |
| High-impact news release (NFP, FOMC) | Manual memory of blackout windows, often missed | EA blocks new trades automatically during the window |
| Multiple open trades across pairs | Trader mentally totals floating loss, often too slow | EA sums real-time floating P/L continuously |
| Daily loss limit reset each server day | Unclear when trading is "safe" to resume | Alert confirms reset time and clears trading lock |
| Signal-copy service opens oversized lots | No cap, one bad signal can breach the account | Lot-size cap rejects orders above the configured limit |
| Consistency rule (no single day too large a share of profit) | Rarely tracked manually | EA flags and can restrict trading once threshold is near |
What it costs and what is included
| Item | Price | Notes |
|---|---|---|
| Guardian EA setup (one-time) | $149 | Rule mapping, calibration, VPS install, walkthrough |
| Monthly care plan | $19/month | Rule updates when firm terms change, re-configs for new accounts, alert monitoring support |
| VPS hosting | Billed by provider | Client's own VPS or a recommended provider, paid directly by client |
| Telegram/WhatsApp | Free / standard rates | No extra platform fee for alerts |
No lock-in — the care plan can be cancelled monthly, and the EA continues running on the client's own MT5 terminal either way. The logic behind the setup fee is straightforward: one avoided daily-loss breach on a funded account typically covers the setup cost many times over, since challenge fees and funded payouts both depend on the account staying alive. In our experience, the monthly plan pays for itself the first time a prop firm updates its rulebook and the EA needs re-calibrating rather than the trader discovering the change the hard way.
Delivery timeline
Day 0 — Kickoff
Rules gathered, account size and firm confirmed, alert channel chosen.
Day 1 — Build
EA parameters configured and tested against the client's specific firm rules; soft-stop buffer calibrated.
Day 2-3 — Install and go-live
VPS install, alert channel connected, 15-minute live walkthrough, EA goes live monitoring the account.
What you need to have ready
- Prop firm name and the account's exact daily loss and max drawdown limits (from the firm dashboard or rulebook)
- Account size and currency
- MT5 login credentials for the account (or access to provide them securely during the walkthrough)
- VPS access, or confirmation you'd like a recommendation
- Any consistency rule, news-blackout, or minimum trading days requirement specific to your firm
- Preferred alert channel: Telegram or WhatsApp number
- Confirmation the firm's terms of service permit third-party risk-management EAs (most do; a few restrict automation — worth checking your firm's current rulebook)
Doing it yourself vs done-for-you
| Factor | DIY (manual or free EA) | Prop-Firm Guardian EA |
|---|---|---|
| Setup time | Hours to days researching MQL5 forums and free scripts | Live in 2-3 days, configured to your exact firm rules |
| Rule accuracy | Manual entry, easy to misread firm's daily reset time or currency basis | Mapped directly from firm rulebook during kickoff |
| Ongoing maintenance | You track every firm rule change yourself | Care plan updates configuration when firm terms change |
| Alerting | Often none, or basic MT5 push notifications only | Telegram/WhatsApp breach alerts plus daily summary |
| Cost | Free EA scripts, but your time and risk of misconfiguration | $149 setup + $19/month, fixed scope |
| Best for | Traders comfortable reading MQL5 code and testing thoroughly | Traders who want it done correctly once, without ongoing tinkering |
A capable, patient trader can build a version of this themselves — MQL5 has an active community and free equity-stop scripts exist. The tradeoff is time spent testing edge cases (spread spikes, partial closes, weekend gaps) and the risk of a misconfigured threshold on a live funded account.
Compliance and risk notes
- Confirm your prop firm's current terms of service permit third-party EAs or risk-management tools on funded accounts — policies vary by firm and change over time.
- The EA closes positions automatically once a threshold is reached; this is a risk-management action, not investment advice, and does not guarantee a challenge pass or account survival.
- Alert delivery over Telegram/WhatsApp depends on those platforms' own uptime and your internet connection at the VPS location — treat alerts as a notification, not the sole safeguard.
- VPS provider selection should account for server location relative to your broker for low-latency execution and for the data residency preferences of your own jurisdiction.
- Soft-stop buffers reduce but do not eliminate breach risk during extreme slippage or gap events; no automated system can guarantee execution at an exact price.
- This is a general informational overview, not legal or financial advice — check your specific firm's rulebook and your local regulatory requirements before relying on any automated risk tool.
Mistakes buyers make
- Using the firm's stated limit as the EA's stop level. Fix: set the soft-stop buffer below the hard limit so slippage doesn't cause a breach anyway.
- Forgetting to update the EA after a firm changes its rules. Fix: keep the care plan active so re-configuration happens as soon as terms change.
- Running the EA on a home computer instead of a VPS. Fix: install on a stable, always-on VPS so a power cut or closed laptop doesn't disable protection.
- Assuming the EA replaces a trading strategy. Fix: understand it only enforces limits — it doesn't pick trades or manage a signal-copy service's logic.
- Not testing the alert channel before going live. Fix: confirm Telegram/WhatsApp alerts arrive during the walkthrough, not after the first real breach.
FAQ
Does this work with any prop firm, or only specific ones?
It's built to be configured to any firm's published numeric rules — daily loss, drawdown, consistency, news restrictions. FTMO, FundedNext, and The5ers are common examples, but the same approach applies to other firms with comparable rule structures.
Will it interfere with my existing EA or signal-copy service?
No. Guardian EA runs alongside your existing trading logic and only intervenes — closing trades or blocking new orders — when your configured limits are actually approached.
What happens if my prop firm changes its rules mid-challenge?
The monthly care plan covers re-configuration when firm terms change, so the thresholds stay accurate without you needing to track every rulebook update yourself.
Can it auto close trades at daily loss limit even if I'm not at my computer?
Yes — that's the core function. It runs continuously on your VPS and closes positions the moment your configured threshold is reached, regardless of whether you're online.
Do I need to give you my MT5 password permanently?
Access is needed during the install and walkthrough to configure the EA on your terminal; how credentials are handled and stored should be confirmed directly with the team during kickoff.
What if I want to cancel the care plan later?
There's no lock-in — the care plan is month to month, and the EA keeps running on your own terminal and VPS regardless of whether you continue the plan.
Next step
Email support@bharataisaathi.com or message WhatsApp with your prop firm name, account size, and daily loss/drawdown limits to start. See the full offer details on the Prop-Firm Guardian EA page, or read how we work before kickoff.
Prop-Firm Guardian EA
Third-party platform and model usage billed to you directly. No lock-in. Live in 3 days.