Generate a real (not estimated) token usage and cost report from Claude Code
AI agents call usage_report to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and reports on usage metrics and costs—it reads historical data to produce a report. There is no indication of modification, deletion, or execution of commands. It is purely observational/analytical, making it a Read category tool with low severity since misuse would only expose usage information without enabling destructive or financial actions directly.
From the tool's definition Tool 'usage_report' generates a report from Claude Code with 'token usage and cost' data. The verb 'generate' combined with 'real (not estimated)' indicates retrieval and aggregation of existing data without modification. No side effects are described.
Documented attack patterns abuse exactly the kind of access usage_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for usage_report:
{
"version": "1",
"default": "deny",
"tools": {
"usage_report": {}
}
} usage_report 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.
Generate a real (not estimated) token usage and cost report from Claude Code. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for usage_report: 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 Claude Code Toolkit. Nothing to install.
usage_report 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_report 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_report. 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_report is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.