The issue is in your policy configuration
When I try it out it does not keep any rate limit and passes as many requests per second without any restrictions.
Maybe the word partition in the policy definition might be confusing. But your configuration is literally telling the key not to apply the rate limit in the policy.
If you change this value to true, it would apply the rate limit in the policy. If false, it would ignore the rate limit in the policy.
Can you try setting "rate_limit": true and test the outcome?