Reset daily token usage counters
AI agents call reset_daily_usage to permanently remove resources in OpenAI Token Manager MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Resetting daily usage counters destroys the historical tracking data for that day, which cannot be recovered. This is an irreversible deletion of usage records. While the blast radius is moderate (loss of token tracking data, potential for cost estimation errors), it doesn't affect financial transactions or code execution directly.
From the tool's definition 'Reset daily token usage counters' — resets/clears accumulated usage data irreversibly
Attacks that exploit this kind of access
Reset daily token usage counters. It is categorised as a Destructive tool in the OpenAI Token Manager MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenAI Token Manager MCP server in PolicyLayer and add a rule for reset_daily_usage: 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 OpenAI Token Manager MCP. Nothing to install.
reset_daily_usage 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 reset_daily_usage 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 reset_daily_usage. 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.
reset_daily_usage is provided by the OpenAI Token Manager MCP server (opaldecisionsciences/openai-token-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →