delete_usage_limit
Delete a usage limit by id. This is permanent, removes the budget immediately, and clears tracked usage state; check list_usage_limit_entities first if you need impact.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-usage-limit.md
What delete_usage_limit does on Portkey Admin
AI agents call delete_usage_limit to permanently remove resources in Portkey Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_usage_limit is rated Critical
This tool permanently deletes usage limit configurations and clears associated tracking state. The effects cannot be undone—deletion is explicitly permanent. This is a classic Destructive action as it irreversibly removes data.
From the tool's definition Tool description explicitly states: 'Delete a usage limit by id. This is permanent, removes the budget immediately, and clears tracked usage state.' The words 'Delete', 'permanent', and 'removes' indicate irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_usage_limit 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 delete_usage_limit, this is the rule to start with:
delete_usage_limit is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every delete_usage_limit call is checked against it from then on.
Questions about delete_usage_limit
Delete a usage limit by id. This is permanent, removes the budget immediately, and clears tracked usage state; check list_usage_limit_entities first if you need impact. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for delete_usage_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 Portkey Admin. Nothing to install.
delete_usage_limit is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_usage_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 delete_usage_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.
delete_usage_limit 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.
Across the catalogue