Fetch real-time Claude.ai subscription usage (5h session and 7d weekly utilization, reset times, extra credits) from the same endpoint Claude Code
AI agents call usage_status to retrieve information from Mcp Token Saver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves subscription telemetry and status information without creating, modifying, deleting, or executing any operations. The data fetched (usage statistics and reset times) is informational only. No financial transactions, code execution, or irreversible changes are possible. Low severity because misuse would only expose usage data already available to the authenticated user.
From the tool's definition Tool name 'usage_status' and description 'Fetch real-time Claude.ai subscription usage' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access usage_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Token Saver, and nothing reaches the server without passing your rules. This is the rule we recommend for usage_status:
{
"version": "1",
"default": "deny",
"tools": {
"usage_status": {}
}
}usage_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch real-time Claude.ai subscription usage (5h session and 7d weekly utilization, reset times, extra credits) from the same endpoint Claude Code. It is categorised as a Read tool in the Mcp Token Saver MCP Server, which means it retrieves data without modifying state.
Register the Mcp Token Saver MCP server in PolicyLayer and add a rule for usage_status: 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 Mcp Token Saver. Nothing to install.
usage_status 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 usage_status 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 usage_status. 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.
usage_status is provided by the Mcp Token Saver MCP server (talap-creator/mcp-token-saver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Token Saver, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Mcp Token Saver tools catalogued and risk-classified — across an index of 43,000+ MCP servers.