# Suspicious IP Throttling for Access Token Request

**URL:** <https://community.auth0.com/t/suspicious-ip-throttling-for-access-token-request/134997>\
**Category:** Get Help\
**Tags:** suspicious-ip-throttling, attack-protection\
**Created:** [May 26, 2024, 4:26am UTC](https://community.auth0.com/t/suspicious-ip-throttling-for-access-token-request/134997 "2024-05-26T04:26:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![akanksha.nichrelay](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/akanksha.nichrelay/32/55455_2.png) [@akanksha.nichrelay](https://community.auth0.com/u/akanksha.nichrelay)\
**Post date:** [May 26, 2024, 4:26am UTC](https://community.auth0.com/t/suspicious-ip-throttling-for-access-token-request/134997/1 "2024-05-26T04:26:57Z")

</div>

Do the Suspicious IP throttling settings also apply to the brute force or suspicious call to `/oauth/token` for access token request for Client credential grants?

If not, how can we throttle suspicious attempts for access token requests?

---

<div class="post-metadata">

**Author:** ![remus.ivan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/remus.ivan/32/68771_2.png) [@remus.ivan](https://community.auth0.com/u/remus.ivan)\
**Post date:** [April 30, 2025, 3:08pm UTC](https://community.auth0.com/t/suspicious-ip-throttling-for-access-token-request/134997/3 "2025-04-30T15:08:39Z")

</div>

Hi @akanksha.nichrelay,

Welcome to the Auth0 Community! We are answering this questions in hope it will help others as well.

**Brute force protection** or **Suspicious IP throttling** are security mechanisms proivded by Auth0 that check the integrity for end-user accounts and are not specifically designed for M2M requests.

However, to check against suspicious requests when using the Client Credential Grant you can [View Logs](https://auth0.com/docs/deploy-monitor/logs/log-event-type-codes) directly from the Auth0 Dashboard and check for `feccft` event type codes for **Failed exchange of Access Token for a Client Credentials Grant**.

Another way to check against possible suspicious or failed requests in the M2M scenario would be implementing logic in a `credentials-exchange` Action Trigger, since this takes place before an Access Token was issues. You can check out the [Machine to Machine Trigger](https://auth0.com/docs/customize/actions/explore-triggers/machine-to-machine-trigger) documentation.

Best regards,  
Remus

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [May 14, 2025, 3:08pm UTC](https://community.auth0.com/t/suspicious-ip-throttling-for-access-token-request/134997/4 "2025-05-14T15:08:54Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.