Which feature is used to block messages based on rate limits in Edge security?

The feature utilized for blocking messages based on rate limits within Edge security frameworks is API Rate Limiting. This feature is designed to control the number of requests that a client can make to an API within a specified time frame, thereby preventing overload and ensuring equitable resource use among all users.

API Rate Limiting serves several essential purposes: it safeguards the API from excessive traffic, mitigates the risk of potential denial of service attacks, and fosters a smoother experience for users by managing the load on the system. By establishing thresholds for requests, it helps maintain performance and availability of services.

In contrast, the other options either do not specifically address message blocking based on rate limits or focus on broader security aspects. Content Security pertains more to protecting data integrity and confidentiality, while Quality of Service is about managing bandwidth and maintaining service quality but is not specifically limited to rate-based controls. Denial of Service, while related to attacks that can overwhelm an API, does not represent a proactive approach to blocking messages but rather describes a type of malicious action. Thus, API Rate Limiting is the precise feature designed to enforce rate thresholds effectively.