> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/risk/breach-guard.md).
# Breach Guard
Breach Guard steps in before an account crosses a firm limit. You cannot turn it off from the app.
Breach Guard watches every account against its firm's drawdown limits. When an account reaches its safety margin, Breach Guard stops it from getting closer to the limit. You cannot turn Breach Guard off from the app.
## Three actions at the safety margin
The safety margin is a percent of each firm limit. The default is 90%.
| Name | What it means |
| ---------------------- | --------------------------------------------------------------------------------------------------------- |
| **Block new entries** | No new trades open on the account. Closing trades still work. |
| **Auto-flatten** | If open positions would still cross the limit, TradeSurge closes them. |
| **Money-at-risk page** | Once Telegram is paired, you get an urgent alert with what happened. Telegram alerts open with the alpha. |
A flatten only counts as done when the venue confirms the account is flat. If it cannot confirm, TradeSurge retries and alerts you.
## You can tighten it, never widen it
You can move the safety margin anywhere from 50% to 100% of the firm limit, per account. It can never be set past the firm limit, and you cannot turn it off from the app.
## When the rule is unclear, it takes the stricter reading
* If a firm's reset time is unknown, Breach Guard uses a rolling 24-hour window instead of guessing midnight.
* If a firm mixes static and trailing drawdown, Breach Guard uses whichever is tighter.
* If a firm's limit is missing from the catalogue, new entries are blocked, and Breach Guard will not flatten on a limit it cannot compute.
* After a restart, entries stay blocked until a fresh balance reading comes in.
{% hint style="danger" %}
Breach Guard may act early. That is by design: an early flatten costs one trade, a breach costs the account.
{% endhint %}
## Next steps
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tradesurge.co/platform/risk/breach-guard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.