rate_limit
Rate Limit Advisor — Remaining capacity, wait time, and burst headroom for a sliding-window rate limit.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/rate-limit.md
What rate_limit does on Gateway
AI agents call rate_limit to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
used | integer | — | Calls already used this window |
limit | integer | Yes | Calls allowed per window |
planned_calls | integer | — | Calls you plan to make |
window_seconds | number | Yes | Window length in seconds |
Parameters from the server's own tool schema.
Why rate_limit is rated Low
This tool queries the current state of rate limiting parameters and returns advisory information. It has no side effects, does not modify any data, and does not trigger external operations. It is a read-only tool that returns status information, similar to monitoring or observability tools.
From the tool's definition Tool description states 'Remaining capacity, wait time, and burst headroom' — purely informational metrics about rate limit status. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs rate_limit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rate_limit, this is the rule to start with:
rate_limit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every rate_limit call is checked against it from then on.
Questions about rate_limit
Rate Limit Advisor — Remaining capacity, wait time, and burst headroom for a sliding-window rate limit. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
rate_limit accepts 4 parameters: used, limit, planned_calls, window_seconds. Required: limit, window_seconds. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for rate_limit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gateway. Nothing to install.
rate_limit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rate_limit rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for rate_limit. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
rate_limit is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue