list_usage_limit_entities
List the entities currently tracked against a usage limit, including current usage. Use this to see who is near or over budget before reset_usage_limit_entity or delete_usage_limit.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-usage-limit-entities.md
What list_usage_limit_entities does on Portkey Admin
AI agents call list_usage_limit_entities to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_usage_limit_entities is rated Low
This tool retrieves and queries usage limit tracking data to display current usage metrics. It has no capability to modify, delete, or execute operations. The description explicitly frames it as an informational tool for viewing data before potentially taking other actions. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name contains 'list' and description states 'List the entities currently tracked against a usage limit, including current usage' and 'Use this to see' — pure information retrieval with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs list_usage_limit_entities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_usage_limit_entities, this is the rule to start with:
list_usage_limit_entities 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 Portkey Admin, apply this rule, and every list_usage_limit_entities call is checked against it from then on.
Questions about list_usage_limit_entities
List the entities currently tracked against a usage limit, including current usage. Use this to see who is near or over budget before reset_usage_limit_entity or delete_usage_limit. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_usage_limit_entities: 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 Portkey Admin. Nothing to install.
list_usage_limit_entities 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 list_usage_limit_entities 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 list_usage_limit_entities. 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.
list_usage_limit_entities is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue