> For the complete documentation index, see [llms.txt](https://failsafe-1.gitbook.io/failsafe.gitbook.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://failsafe-1.gitbook.io/failsafe.gitbook.io/module-overviews/failsafe-interceptor.md). # FailSafe Interceptor [FailSafe Interceptor ](/failsafe.gitbook.io/frequently-asked-questions/failsafe-guard-faqs/how-does-failsafe-interceptor-work.md)provides a unique value proposition for enterprises – the ability to stop a transaction in its tracks even after an attacker has broadcasted it. This elevates transaction security by operating independently of client-side code paths, ensuring comprehensive visibility over all enterprise transactions about to be imminently confirmed (by monitoring pending transactions across public, private, and internal streams). When FailSafe Interceptor identifies an unauthorized transaction, it swiftly deploys a counter-transaction that transfers at-risk funds to a secure, self-hosted smart contract wallet, which neutralizes the threat and secures assets away from attackers. It achieves this through the following innovations: ## Low-Latency Response Utilizes a globally-deployed infrastructure of servers to monitor memory pools, ensuring rapid detection and response to threats. ### Comprehensive Transaction Visibility * Public and Private Streams: Monitors both public and private pending transaction streams for a broad overview of all potential threats. * Internal Transactions (X-Ray): Monitors smart contracts for internal transactions that do not appear in memory pools, providing deep visibility into contract activities. ### Transaction Ordering FailSafe Interceptor's transactions are prioritized by validators due to higher gas fees, ensuring they are processed before the attacker’s transaction. ### Obfuscation The self-hosted smart contract (Recovery Vault) is deployed only when an unauthorized transaction is detected. This prevents attackers from knowing whether an enterprise is protected by FailSafe Interceptor until it is too late, offering a strategic advantage in cybersecurity. ### Gas Station For enterprises that prefer not to manage gas, FailSafe can cover gas costs on their behalf. FailSafe is then compensated in the same transaction with the token it is protecting. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://failsafe-1.gitbook.io/failsafe.gitbook.io/module-overviews/failsafe-interceptor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.