Issue Description
After using up my 500 rapid requests, I’ve encountered a critical issue with the MCP service. When the request limit is reached, the regular agent functionality continues to work properly, but any attempt to call an MCP tool results in the system hanging permanently with no response or timeout.
Steps to Reproduce
- Use up the 500 rapid request allocation
- Attempt to use any MCP tool function
- Observe that the request never completes or returns any result
Expected Behavior
- Either a clear error message indicating the request limit has been reached
- OR a queue message stating when the request might be processed
- OR some form of degraded but still functional service
Actual Behavior
The system appears to accept the MCP tool request but then hangs indefinitely. The request neither succeeds nor fails - it simply never returns any response. This creates a “zombie” state where the user is forced to restart their session.
Environment Details
- Cursor Version: [Your version here]
- Operating System: [Your OS here]
- Browser (if applicable): [Your browser here]
Additional Context
The regular agent features continue to function correctly, confirming that the issue is specifically related to the MCP tool functionality when request limits are reached, not a general connectivity issue.
Impact
This bug significantly impacts productivity as:
- There is no clear indication that the request limit has been reached
- Users waste time waiting for a response that will never come
- The only workaround is to restart the session, potentially losing context
Any assistance in resolving this issue would be greatly appreciated.
