portkey-admin-mcp

list_rate_limits

Read-onlyIdempotent

Lists rate-limit policies with condition, grouping, unit, target, status, and scope, enabling filtering—including archived policies—before retrieving or updating one.

Instructions

List rate-limit policies with their current condition, grouping, rate unit, target, status, and scope. Filter before retrieving or changing one policy, especially when archived policies should be included.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rate_limits"
  }
}

Input Schema

Name	Required	Description
`type`	No	Filter by counter type
`unit`	No	Filter by reset interval
`status`	No	Filter by active or archived status
`target`	No	Filter by LLM or MCP-tool target
`page_size`	No	Number of policies to return per page
`current_page`	No	Zero-based page number
`workspace_id`	No	Filter by workspace UUID

Output Schema

Name	Required	Description
`ok`	Yes	Whether the tool call succeeded and returned structured data
`data`	No	Structured success payload when ok is true
`error`	No	Structured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.9Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed7 schema fields changedv0.11.5Sep 8, 2026

addedInput schema / properties / current_page

Added value: +{
+  "description": "Zero-based page number",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / page_size

Added value: +{
+  "description": "Number of policies to return per page",
+  "exclusiveMinimum": 0,
+  "maximum": 100,
+  "type": "integer"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Filter by active or archived status",
+  "enum": [
+    "active",
+    "archived"
+  ],
+  "type": "string"
+}

addedInput schema / properties / target

Added value: +{
+  "description": "Filter by LLM or MCP-tool target",
+  "enum": [
+    "llm",
+    "mcp_tools"
+  ],
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Filter by counter type",
+  "enum": [
+    "requests",
+    "tokens"
+  ],
+  "type": "string"
+}

addedInput schema / properties / unit

Added value: +{
+  "description": "Filter by reset interval",
+  "enum": [
+    "rpm",
+    "rph",
+    "rpd",
+    "rpw"
+  ],
+  "type": "string"
+}

changedInput schema / properties / workspace_id / description

Previous value: -"Filter rate limits by workspace ID"New value: +"Filter by workspace UUID"

Addedv1.0.1May 7, 2026
RemovedMay 1, 2026
First observedJan 1, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The only added behavioral signal is the note that archived policies need attention when filtering, implying they aren't returned by default; pagination defaults and ordering are not disclosed, and the field list largely restates the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action front-loaded and the usage hint second. The attribute enumeration ('condition, grouping, rate unit, target, status, and scope') is somewhat redundant given the output schema and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, rich annotations, and fully documented parameters, the description only needs to supply intent and selection guidance, which it does. A little more on default filtering behavior (archived inclusion/exclusion) and result ordering would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all four enum parameters are self-documented (type, unit, status, target), so the baseline of 3 applies. The description only loosely alludes to filters ('rate unit, target, status') and adds nothing about page_size/current_page or workspace_id beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('List') plus resource ('rate-limit policies') and enumerates the attributes returned (condition, grouping, rate unit, target, status, scope). It implicitly points at the single-policy counterpart by saying it is for filtering 'before retrieving or changing one policy', though it never names get_rate_limit/update_rate_limit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear use case: filter here first to locate a policy before retrieving or mutating it. It also flags that archived policies must be considered explicitly, which is a genuine selection condition, but falls short of explicitly naming the sibling tools or stating when NOT to use it (e.g., when the ID is already known).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server