usage_history
Context-safe usage audit query. Defaults to aggregated summary, supports precise search by execution_id/search_id/charge_outcome/credit range, and writes large exports to a local JSONL file instead of returning all rows.
This record as markdown: /tools/qverisai-qveris-agent-toolkit/usage-history.md
What usage_history does on Qverisai
AI agents call usage_history to retrieve information from Qverisai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why usage_history is rated Low
The tool retrieves historical usage and audit information with optional filtering parameters (execution_id, search_id, charge_outcome, credit range) and outputs results either as summaries or exports. This is a classic read operation with no side effects on the underlying system state or financial transactions.
From the tool's definition Tool description explicitly states 'audit query' and 'search', with outputs either returned as aggregated summary or written to local file. No modification, deletion, or execution of external operations—purely data retrieval and reporting.
Attacks that exploit this kind of access
The rule that runs usage_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Qverisai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usage_history, this is the rule to start with:
usage_history 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 Qverisai, apply this rule, and every usage_history call is checked against it from then on.
Questions about usage_history
Context-safe usage audit query. Defaults to aggregated summary, supports precise search by execution_id/search_id/charge_outcome/credit range, and writes large exports to a local JSONL file instead of returning all rows. It is categorised as a Read tool in the Qverisai MCP Server, which means it retrieves data without modifying state.
Register the Qverisai MCP server in PolicyLayer and add a rule for usage_history: 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 Qverisai. Nothing to install.
usage_history 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_history 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_history. 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_history is provided by the Qverisai MCP server (qverisai/qveris-agent-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Qverisai, and thousands of servers like it.
This server
Across the catalogue