Keeping an ICT EA Compliant with News Trading Rules – A Practical Guide

It’s 8:45 AM, five minutes before the U.S. Consumer Price Index (CPI) release. Your ICT Expert Advisor has just identified a textbook Fair Value Gap (FVG) setup on the 5-minute chart. The displacement candle is forming, the order block is holding, and the algorithm is ready to enter. But you hesitate. Your prop firm’s compliance dashboard flashes a warning: No trading in the 2-minute window before and after high-impact news.

You make the call – you disable the EA manually. The news hits, price spikes 50 pips in seconds, and when the dust settles, your setup is gone. You avoided a violation – but you also missed the trade. This scenario plays out daily in prop trading, and it highlights the single biggest challenge for traders running automated ICT strategies in 2026: keeping your EA compliant with news trading rules without sacrificing the very setups your strategy was built to catch.

Why News Rules Are the Breaking Point for Automated ICT

The challenge isn’t that ICT traders don’t understand news risk. It’s that ICT execution is mechanical. It relies on precise displacement, break of structure, and liquidity sweep events that often cluster around market openings and major data releases. This is the exact territory where prop firms apply their strictest news restrictions.

Many proprietary trading firms enforce a two-stage protection model: a pre-block window where new trades are prevented (often 15 minutes before the event), followed by an active window where all positions must be closed (sometimes 2 minutes before and after the release). For the ICT trader, this creates a paradox. The post-news displacement is often the highest-probability entry – yet entering during or immediately after can trigger a compliance violation if your EA isn’t configured correctly.

The deeper issue is that most EAs treat news filters as an afterthought. They rely on the MQL5 native calendar, which is frequently disabled on prop firm terminals. Or they hardcode a fixed time block that doesn’t account for the specific events your firm actually restricts (since many firms only restrict NFP, CPI, FOMC, and central bank decisions, while allowing other high-impact events like ISM or PMI). If your EA can’t distinguish between a restricted event and a tradable one, it either blocks too much (killing your edge) or blocks too little (risking a violation).

The Compliance Workflow No One Talks About

The traders who successfully run ICT EAs on funded accounts don’t just code a news filter and forget it. They build a workflow around compliance that includes three layers:

**Layer 1: The EA must know which events are restricted.** This requires a news source that works on your broker’s terminal, because the built-in calendar often doesn’t. Some traders implement a spread-based filter that pauses trading when spreads widen beyond a threshold – a simple but effective method that doesn’t require an external calendar. Others use a ForexFactory feed that’s cached locally and updated every few hours. Either way, the EA needs to know the difference between a restricted event and a non-restricted one – because banning all high-impact news will cost you more trades than the rules themselves.

Layer 2: The EA must obey the block window, but preserve the setup. The common mistake is setting an EA to close all positions the moment the pre-block window starts. This ignores a crucial nuance: most firms only restrict opening new trades during the pre-block window, while existing positions can continue to run. A well-designed EA enters the pre-block state, stops new entries, but doesn’t automatically flatten the trade you took 20 minutes earlier. The compliance team cares about new trade openings and SL/TP triggers during the restricted window, not about positions that were already established.

Layer 3: You need visibility into what your EA is actually doing. This is where most automated traders fall short. If your EA closes a trade due to a news block, you need to know when it happened, why it happened, and whether it was a legitimate action or a false positive. Without that visibility, you’re trusting code to make compliance decisions you can’t audit.

How Camovia Tray Fits into the Compliance Equation

This is where Camovia Tray becomes unexpectedly valuable. The app isn’t a news filter or a risk management tool – but it solves a specific operational problem that makes news compliance harder than it needs to be: visibility into your MT5/MT4 terminal without opening the full interface.

Here’s the reality of running an ICT EA through a news window. You’ve set your filters, you’ve tested them on demo, and you’re confident the EA won’t trade during the restricted period. But you still need to monitor your positions – you need to see if the EA actually closed those trades, if your stop-loss was hit, or if the system is frozen. Opening the full MT5 terminal during a news event is cumbersome. You have to alt-tab through windows, find the terminal, navigate to the trading tab, and check your open positions. During a fast-moving market, that delay means you might miss the next setup entirely.

Camovia Tray moves this visibility to your system tray. With a single mouse hover, you see your open positions – the instrument, direction, lot size, open price, and current profit or loss[citation:PRODUCT_KNOWLEDGE]. You can quickly verify that your EA’s news filter actually worked – did it close the position as expected? Is the equity drawdown within the firm’s daily limit? You can also close positions with a two-step confirmation, which is useful if you spot that the EA entered a trade during a restricted window and you need to close it manually[citation:PRODUCT_KNOWLEDGE].

The operational advantage is that you’re not fighting your terminal. You’re not scrolling through charts to find your trade. You’re checking your positions from a tool that sits unobtrusively in your system tray, and when you’re done, you can hide the MT5/MT4 window entirely[citation:PRODUCT_KNOWLEDGE]. This reduces the cognitive load during high-stakes news events and lets you focus on what actually matters – the next setup.

Critically, Camovia Tray reads all data locally from your terminal. Nothing is sent to a server, so your positions and equity are not exposed to any third-party service[citation:PRODUCT_KNOWLEDGE]. For a prop trader who’s already under compliance scrutiny, this matters – you’re not introducing a new data leak point into your workflow.

The Bottom Line

Keeping an ICT EA compliant with news trading rules isn’t just about writing code that blocks entries during specific windows. It’s about building a workflow that gives you confidence in that code, visibility into your positions, and the ability to intervene quickly if something goes wrong. Camovia Tray addresses the operational friction that makes news trading compliance harder than it should be. It’s not a replacement for a well-designed EA – but it’s a tool that lets you manage your terminal more efficiently during the most stressful moments of your trading day.

If you’re running an automated ICT strategy on a prop account, your EA handles the execution. Camovia Tray handles the awareness. And in a market where the difference between a compliance violation and a profitable trade comes down to seconds, that awareness makes a real difference.