Kubescape Rate Limits
Neither the open-source Kubescape tool nor the hosted ARMO Platform Customer API publishes fixed numeric request-rate limits. For the open-source CLI and in-cluster Operator, scan throughput is bounded only by your own cluster and host resources. For the hosted ARMO Platform Customer API (https://api.armosec.io/api/v1), the effective ceiling is the plan's worker- node / data-retention allowance rather than a documented per-minute request cap; expect standard HTTP 429 throttling and Retry-After handling on the managed service.
Kubescape Rate Limits is the machine-readable rate-limit profile for Kubescape on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, nodes, and scans.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Kubernetes Security, Cloud Native Security, Container Security, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://hub.armosec.io/reference/customer-api
- https://www.armosec.io/pricing/
- https://github.com/kubescape/kubescape
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/kubescape-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.