sc-rate-limiting

Identify missing rate limits and DoS vectors in web applications and APIs.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-rate-limiting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-rate-limiting
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-rate-limiting
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-rate-limiting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps identify missing rate limits and DoS vectors to protect web apps and APIs.

Core Features & Use Cases

  • Missing rate limit detection on sensitive endpoints (login, password reset, signup, OTP)
  • ReDoS and unsafe pattern detection in regex usage
  • Pagination and payload size abuse detection; actionable remediation guidance

Quick Start

Run the rate-limiting scanner against your web service to detect missing limits and abuse risks.

Frequently Asked Questions about sc-rate-limiting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find missing rate limits on login and password reset endpoints?

To detect missing rate limits on login and password reset endpoints, scan your web service to analyze sensitive API paths for abuse risks. The scanner outputs structured findings with severity levels and actionable remediation steps to secure unbounded access attempts.

What is ReDoS and how does unsafe regex usage create DoS vectors?

ReDoS occurs when unsafe regex patterns cause catastrophic backtracking during evaluation, creating a DoS vector. Scanning your codebase detects these unsafe patterns, preventing attackers from freezing your application through crafted malicious input payloads.

How do I detect unbounded pagination and excessive payload abuse in my APIs?

Detect unbounded pagination and excessive payload abuse by analyzing data-intensive paths in your web application. This identifies API endpoints susceptible to resource exhaustion, providing structured findings with severity ratings and specific remediation guidance to prevent abuse.

Can I use this scanner to check API security for OTP and signup endpoints?

Yes, you can scan OTP and signup endpoints to identify missing rate limits and DoS vectors. The analysis covers common attack surfaces like sensitive authentication paths, surfacing abuse risks and recommending appropriate throttling protections.

What is the best way to identify DoS vectors in web applications?

The best way to identify DoS vectors in web applications is to analyze common attack surfaces such as API endpoints and data-intensive paths. This detects abuse risks like unsafe regex usage and unbounded pagination, outputting structured findings with severity levels and remediation steps.