Forex broker exposure limits translate a brokerage’s risk policy into operating decisions. To be useful, each limit must say what is measured, which trading activity it covers, when it applies and who responds when it is breached. A threshold without those definitions can generate noise rather than control.
This guide explains how to structure exposure policies for an MT4/MT5 dealing desk. It does not prescribe a universal percentage or currency amount. Appropriate limits depend on the brokerage’s risk capacity, execution arrangements and operating model.
Define the metric and its perspective
Start by naming the exposure. Client notional, retained broker exposure and the combined position after external hedges are different measures. Specify whether the figure is signed net, absolute net or gross, and document the treatment of partial allocations and manual hedges.
Use a consistent valuation and reporting currency. Raw lots are not comparable across unrelated contracts. Margin is also a separate calculation: MetaQuotes documents instrument-dependent margin methods, so account margin should not silently become the definition of brokerage exposure.
Set the scope before the threshold
A policy can apply to the whole brokerage, a symbol, a book, an account group or an individual source. State the scope directly in the rule and in its alert. A limit tested against one server should not be labelled as a brokerage-wide control.
Preserve instrument mappings and source identities. A consolidated symbol view can be useful, but the reviewer still needs to inspect the original contracts and accounts contributing to the exposure. See the multi-server risk management guide for the controls behind that consolidated picture.
Keep concentration limits distinct from absolute limits
A currency-denominated limit measures magnitude, while a concentration limit measures a share of a defined total. They answer different questions. Show the numerator, denominator and scope of every concentration measure, especially where offsetting positions change the denominator.
If a symbol represents $2.4 million of absolute exposure within a consistently defined $6 million gross at-risk book, its share is 40%. It can breach a 35% concentration threshold while remaining below a separate $3 million absolute limit. These thresholds are examples, not recommended settings.
Review small-denominator cases explicitly. A concentration percentage can rise because one symbol grew or because other positions closed. The alert should help the desk distinguish those situations instead of implying they are the same event.
Define trigger, acknowledgement and recovery
Specify when an observed breach becomes an alert. Depending on the policy, the desk may need to distinguish a brief update from a sustained condition. Document the observation window and ensure it does not conceal a material exposure change.
Define acknowledgement, assignment and escalation separately from recovery. Acknowledging an alert does not mean the exposure returned within policy. Likewise, a recovered value should not erase the history of the breach or the decisions taken while it was active.
To reduce repeated alerts near a threshold, a policy may use a different recovery boundary or a defined recovery period. Record these settings and explain them in the alert detail. They should be deliberate policy choices, not hidden behaviour.
Make the alert explain itself
- Metric, scope, units and sign convention.
- Configured threshold and observed value.
- Trigger time and source freshness.
- Contributing symbols, books and accounts.
- Assigned owner, response status and recovery condition.
Show when a monitor is disabled or a source is stale. “No alerts” is not evidence that the book is healthy if the required rule is inactive or its data is incomplete. Keep missing-data warnings visible alongside market-risk alerts.
Test the policy before relying on it
Replay known scenarios: a clear breach, a near-threshold fluctuation, a source disconnect and a concentration change caused by other positions closing. Confirm the calculation and the response path with the people who will operate the policy.
Review thresholds when the brokerage’s activity, instrument mix or liquidity arrangements change. Preserve the version of the policy that applied at the time of each alert so a later review can reproduce the original decision.
The BrokerCNC Exposure Monitoring demo connects concentration, contributing accounts and policy alerts. Combine it with the exposure monitoring guide, then arrange a live demo to discuss the definitions and controls your desk needs.
Common exposure-policy questions
Is there one correct concentration threshold for every broker?
No. The threshold must fit a documented policy, a defined exposure calculation and the brokerage’s own risk capacity.
Should acknowledging a breach clear the alert?
Acknowledgement records that someone is handling it. Recovery records that the observed condition has returned within the policy’s defined boundaries.
See the workflow in BrokerCNC.
Discuss your MT4/MT5 servers, operating priorities and the evidence your team needs.
Book a Live Demo →





