Agent Rate Limiter MCP Server

The MCP server implements rate limiting with tiered authentication via API keys and basic access control. However, there are several security concerns that prevent a higher score: unsafe network calls with hardcoded URLs and no timeout protections, unencrypted in-memory state storage without persistence guarantees, missing input validation on critical parameters, and weak credential handling in the fallback auth path. The server also makes unauthenticated external API calls and logs sensitive metadata. While the core functionality matches its stated purpose and permissions are reasonable for a rate-limiting service, the implementation has multiple medium-severity vulnerabilities that should be addressed before production deployment. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 15 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.